This editor sends Elasticsearch SQL, not the query DSL
There are no writes in this grammar at all, no second page, and a trailing semicolon is a syntax error, so the list of edges is the useful part.
4 posts
Writing on Elasticsearch
Query DSL and browsing over indices, with mapping introspection and cluster health. Where it stops: Search engines are query-and-browse: no row editing, no ER diagrams.
The mapping is the schema, and selecting everything is not
An index that maps container fields answers a select-everything statement with no columns at all, so the schema tree is built from the mapping instead.
When the index says two documents and the query says one
Nested elements are stored as documents of their own, so the panel and the editor legitimately disagree, and one panel asks the cluster nothing at all.
Connecting to Elasticsearch with four fields and no database
An index has no namespace above it, so a database selector would be a control with no effect, and a self-signed cluster certificate has nowhere to go here.