We're approaching the first release of our product and we use ElasticSearch
as a key component in our system. But there's still some questions and
doubts so I'd like to listen to the more experienced users and
ElasticSearch folks here.
We use ElasticSearch as a search tool but also the storage of all
documents. It means that the front-end retrieves fields from ES just as if
it's a database. We've already disable the index (index: no) on the fields
that don't need to be searched (list of ids etc.) but is this a good usage
of ElasticSearch? Given that we expected to have ~ 1 billion documents (~
1.4kb each) in our first 3 months in a single index.
We will use thrift to push documents in production because we've seen a
performance gain. Is there any downside of using thrift over plain json?
Some of our queries uses regexp filter. In my comprehension this needs
to load the target field of every document to see if it matches, so it's
pretty costly for an index of 1 billion docs?
We're also benchmarking our ES setup but your advice and experience are
very appreciated! Thanks in advance!
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/563d3c8f-cb3c-4c8c-a13d-2f8fcf6c42ce%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.