elasticsearch

The Elasticsearch-compatible API

Available on dedicated deployments. Start with current support and authentication. JavaScript examples use the 7.x client: request payloads go in body, and responses are read from body. Standalone query fragments belong inside the request body.

OriginChainDB implements an Elasticsearch-compatible REST API and Query DSL subset on dedicated deployments. Index documents, search and aggregate them, and test the operations your application uses against the supported surface.

Quickstart

Connect a client and run your first search, end to end, in about five minutes.

Indexing

Create an index, and decide what each field does - searchable text, exact keyword, or both.

The Query DSL: match, bool, term, range, fuzzy, sorting and paging.

Aggregations

Terms, metrics, date histograms, named filter buckets and top hits.

Suggest

Did-you-mean over the words actually indexed in a field.

Bulk + concurrency

Load many documents fast, and guard a write so it lands only if nobody changed the document first.

By industry

Worked examples: product catalog, application logs, transactions, support tickets.

All examples

Sixteen copy-paste recipes, each one request and its response.

What you point at it

Use a compatible Elasticsearch 7.x client or plain HTTP. The endpoint reports version 7.14.2. Use the complete tenant endpoint as the client base URL; each index lives under that path.

POST /v1/tenants/:tenant/es/:index/_search
PUT  /v1/tenants/:tenant/es/:index/_doc/:id
POST /v1/tenants/:tenant/es/_bulk

What makes it different from a search cluster

No sync, no lag. A document is written by the same transaction that writes the row, so it is searchable the instant the call returns. There is no refresh interval to wait on and no connector to keep running.
Your policies apply to the search. Row-level security and column masking are enforced on the query itself, not just on the documents it returns. A caller who cannot see a row will not find it, and a query against a masked column is refused rather than answered.
One store. The same data answers SQL, the HTTP API, vector search and this. Nothing is copied anywhere.

What it does not do

Coverage is limited to the documented API subset. Unsupported bodies can return errors, while unknown URL parameters are currently ignored. Check the supported options explicitly; HTTP success alone does not prove that every option was applied.

Area	Answered	Refused, and why
Aggregations	terms, metrics, range, histogram, date_histogram, percentiles, top_hits, filters, sub-aggregations, pipelines, extended_stats	composite, nested have no executor yet; missing on a metric aggregation would fill in a value you did not choose
Suggesters	the term suggester, with suggest_mode	phrase and completion have no executor; popular ranks by a document frequency this API does not report
Paging	search_after, scroll and Point-in-Time	Check the deployment limits in `/v1/capabilities`
Scoring	function_score, per-field boosts	script_score and rescore would run arbitrary script
Cluster management	index create, delete, mapping, _field_caps, legacy and composable templates	ILM and snapshot administration are not supported over this API

Vector and hybrid search live on their own surface — see querying.

Elasticsearch is a trademark of Elasticsearch B.V., registered in the U.S. and in other countries. OriginChainDB is not affiliated with, endorsed by, or sponsored by Elasticsearch B.V. OriginChainDB implements a compatible HTTP API so that existing Elasticsearch clients can talk to it; it does not distribute Elasticsearch software.