Databases 6 min read

A 20 MB DBX Client That Fully Handles Easysearch and Elasticsearch

DBX is a lightweight ~20 MB client that natively supports Easysearch and Elasticsearch, offering quick Windows installation, graphical connection setup, SQL and native DSL query editors, and a visual filter panel, making index inspection and data retrieval fast and convenient.

Mingyi World Elasticsearch
Mingyi World Elasticsearch
Mingyi World Elasticsearch
A 20 MB DBX Client That Fully Handles Easysearch and Elasticsearch

Why written

Existing Elasticsearch tools are either large (hundreds of MB, slow startup) or lack native Easysearch support, forcing users to switch to Kibana or curl for simple queries.

Installation

The Windows installer is a standard Nullsoft package. Selecting a directory and proceeding through the wizard installs the client in under 60 MB of disk space.

Creating an Easysearch connection

In the client click New Connection . In the left‑hand category list choose Document/Cache/Search , then select Easysearch . Fill the fields:

Host + Port : Easysearch node address, default 9200.

Username/Password : Use the admin account when security is enabled.

URL parameters : e.g. sslmode=prefer for HTTPS without extra configuration.

Alternatively paste a full URL such as https://user:password@host:port to auto‑populate the fields.

Index view after connection

Successful connection lists all Easysearch indices in the left pane. Clicking an index opens a table view where each document is a row and each field a column. Field types (keyword, text, double, date) appear beneath column headers. A JSON view button shows the raw document structure.

Query method 1: SQL

The built‑in SQL editor uses Easysearch’s SQL plugin. Example queries:

select * from bank_transactions as bt;
select * from bank_transactions as bt where 客户姓名 = '韩泽';

Results are displayed in the same table component with pagination, column sorting, and export options.

Query method 2: native DSL

For complex bool logic or multiple clauses, write Elasticsearch DSL directly. Example request body:

POST /bank_transactions/_search
{
  "query": {
    "match": {
      "客户姓名": "杨军"
    }
  }
}

The table rendering and field metadata are shared with the SQL view, so switching between SQL and DSL does not affect the user experience.

Query method 3: visual filter

The graphical Filter panel lets users add conditions without writing code. Example conditions: 交易地点 (keyword) = 北京 交易对手姓名 (keyword) wildcard = 李

Filters are combined with AND logic; clicking Apply Filter translates the UI selections into DSL behind the scenes.

Summary

For routine Easysearch/Elasticsearch tasks—data lookup, index verification, and issue diagnosis—the client provides a three‑layer solution:

Connection layer : graphical configuration with support for authentication, SSL, and one‑click URL import.

Query layer : SQL, DSL, and visual filter coexist, allowing users to choose the most suitable method.

Display layer : combined table and JSON views with visible field types.

Package size (~20 MB) and fast startup eliminate the need for heavyweight tools. Download URL: https://dbxio.com/cn

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

DSLSQLElasticsearchlightweightEasysearchDBXsearch client
Mingyi World Elasticsearch
Written by

Mingyi World Elasticsearch

The leading WeChat public account for Elasticsearch fundamentals, advanced topics, and hands‑on practice. Join us to dive deep into the ELK Stack (Elasticsearch, Logstash, Kibana, Beats).

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.