Search

Elasticsearch

Elasticsearch focuses on search DSL builders, mappings, shard/profile diagnostics, explicit-id document edits, and guarded index/admin previews.

Available12 minDesktop

Prerequisites

  • Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
  • Have the endpoint, database file, or cloud account details for a Elasticsearch datastore you are authorized to use. Start with least-privileged, read-only access.
  • Keep an independent backup before enabling edits, administration, restore, or transfer execution.

Connect and run a safe query

  1. 1

    Create the connection

    Open Library, choose Create connection, and select Elasticsearch and a supported Connection method tab.

  2. 2

    Test and save

    Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.

    Elasticsearch connection setup. The Elasticsearch connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving.
    Elasticsearch connection setup. The Elasticsearch connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size
  3. 3

    Open the native explorer

    Use Save Connection, or Create Database and Save Connection for a new local file, then open the Elasticsearch Explorer where supported.

  4. 4

    Select a scope

    Select the index / alias scope that should be attached to the new tab.

  5. 5

    Run a bounded read

    Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.

    Elasticsearch native workflow. A representative Elasticsearch explorer and bounded read-only workflow. Replace the example objects with names from your datastore.
    Elasticsearch native workflow. A representative Elasticsearch explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size
  6. 6

    Inspect the result

    Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.

  7. 7

    Export when needed

    Export only the required rows after reviewing format, destination, and redaction options.

  8. 8

    Open diagnostics or transfers

    Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.

Connection fields

FieldRequiredPurposeSafe example
NameYesA clear profile name, without credentials.Elasticsearch development
Connection methodYesChoose a supported tab. The fields below apply only to the selected method and deployment.Connection fields / Connection string
EnvironmentNoAttach the intended variable and safety context.Local development
Read-only connectionNoEnable for initial exploration. This does not make pre-release software safe for production workloads.Enabled
Host / PortNoEndpoint for a fields-based connection. Follow the selected deployment and runtime limitations; MongoDB SRV does not use an explicit port.localhost / engine default
Database / default scopeNoInitial scope for browsing, where supported.catalog
Complete connection stringYesRequired in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value.Paste your complete provider string; do not share it
UsernameNoAuthentication identity for the selected method.catalog_reader
PasswordNoRequired only when the chosen authentication needs it. Save Connection stores changes; blank preserves an existing value, and Reveal… explicitly discloses it.Stored in the desktop OS vault
AuthenticationNoAuthentication. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.none / basic
EndpointNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Default indexNoGeneral. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Path prefixNoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default
Request timeout (ms)NoAdvanced. Optional, depending on the method and server. Review runtime limitations before overriding the driver default.Driver default

Run the sample query

Elasticsearch read-only example
GET products/_search
{
  "size": 25,
  "query": { "term": { "active": true } }
}

Explore and inspect

  • Browse indexes, mappings, aliases, data streams, field capabilities, shard health, lifecycle state, search result structures, templates, pipelines, and diagnostics.
  • Inspect hits, _source documents, highlights, aggregations, profile stages, shard details, raw JSON, and explicit-id document edit evidence.

Diagnose, administer, and transfer

  • Review cluster health, field capabilities, shard health, Lucene segments, lifecycle state, ingestion posture, security posture, slow-log settings, allocation, and normalized profile stages.
  • Preview force merge, cache clear, reindex, open/close, mappings, settings, aliases, templates, pipelines, rollover, lifecycle policy, task cancel, snapshot/restore, bulk, security, slow-log, and allocation workflows.
  • Import — Live. Elasticsearch exports with PIT/search-after and imports into a new rollback-safe index through conflict-safe Bulk create actions. Formats: Search transfer folder (native). Destinations: local folder.
  • Export — Live. Elasticsearch exports with PIT/search-after and imports into a new rollback-safe index through conflict-safe Bulk create actions. Formats: Search transfer folder (native). Destinations: local folder.
  • Backup — Live. Elasticsearch uses configured snapshot repositories. Formats: Native snapshot (native). Destinations: repository.
  • Restore — Live. Elasticsearch uses configured snapshot repositories. Formats: Native snapshot (native). Destinations: repository.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action.
Transfers Center. Transfers Center shows a failed example transfer with its warning count, failure detail, retry control, and dismiss action. Open full size

Capabilities and availability

CapabilityStatusNotes
Native explorerAvailableBrowse indexes, mappings, aliases, data streams, field capabilities, shard health, lifecycle state, search result structures, templates, pipelines, and diagnostics.
Read queriesAvailableUse visual Query DSL helpers for filters, source fields, sorting, terms/date-histogram/histogram/metric/cardinality aggregations, raw DSL, profile, and explain payloads.
Inline editingGuardedRequires key evidence, a writable profile, and environment confirmation.
Diagnostics / administrationGuardedPreview force merge, cache clear, reindex, open/close, mappings, settings, aliases, templates, pipelines, rollover, lifecycle policy, task cancel, snapshot/restore, bulk, security, slow-log, and allocation workflows.
Import / export / transferGuardedAvailability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented.

Safety and limitations

Troubleshooting

SymptomResolution
Test connection fails or times outVerify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure.
Explorer branches are empty or disabledConfirm the selected index / alias, refresh the branch, and grant the minimum metadata permissions described in the connection warning.
Run, edit, admin, or transfer is disabledRead the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback.
The sample query fails or returns different columnsReplace the example names with objects from your Elasticsearch datastore, confirm the selected index / alias, and keep the query bounded while you validate the result.