The current mirage workflow is designed in an opinionated fashion to programmatically compose Elasticsearch Query DSL compatible queries. As a result, it defaults to starting out with a compound query (bool clause).
We are leaving out the use-case of teaching Elasticsearch query syntax currently.
It would be ideal if we can figure a way to compose queries that start out with a leaf query format and change to compound query (bool format) when a compound condition or nesting is added. And when that compound condition or nesting is removed, it reverts to the leaf query format.
The current mirage workflow is designed in an opinionated fashion to programmatically compose Elasticsearch Query DSL compatible queries. As a result, it defaults to starting out with a compound query (
boolclause).We are leaving out the use-case of teaching Elasticsearch query syntax currently.
It would be ideal if we can figure a way to compose queries that start out with a leaf query format and change to compound query (bool format) when a compound condition or nesting is added. And when that compound condition or nesting is removed, it reverts to the leaf query format.