Hacker News new | ask | show | jobs
by tarjei 2170 days ago
One of the things I find so confusing with Elasticsearch is querying. Constructing a complex JSON document for a simple query just doesn't fit my brain. I have tried to put this down to bad/confusing documentation, but I'm not sure anymore.

It seems Redis is moving a bit in the same direction - although not as complex as ES has done it.

Being able to run this inside a Redis instance is a big win, although I suspect few/none of the cloudproviders are willing to pay RedisLabs for the privelige of using the module.

4 comments

For my standard use-cases using the query_string query is "good enough", it is the only thing I regularly implement and expose to users. That + some pre-defined aggregations gets you very far. Query String Query can do things like boolean operations (AND, OR, NOT), phrase search, fuzzy search, range search, date math, regex search, boosting: https://www.elastic.co/guide/en/elasticsearch/reference/curr...
Agreed. The JSON query syntax is nonsensical. I much prefer the simpler Lucene style syntax.
RediSearch is available on all the big clouds as a managed solution