Hi,
I'm evaluating ES features by reading the doc. Here is the missing usecase I was not able to find in the documentation. I want to perform query in an index from 2 differents applications. One application needs NRT view of the index. And another needs a more stable view of the data (refreshed every day or hour, it depends on application needs). With raw Lucene it's quite easy to implement such feature : - Keep one IndexReader open for the stable view + NRT : drawback is that I loose my IndexReader if the application restarts - Use IndexCommit and IndexDeletionPolicy for the stable IndexReader, it supports app restart. Does ES supports these lucene features : keep a commit point, open a reader on that particular commit (and delete the index commit when it's no more needed)? As the base feature is part of Lucene API would it be hard to implement such feature into ES? (I suspect scroll api to already keep an opened IndexReader under the hood, isn't it possible to generalize it to the query API?) Thanks. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4b082651-51e6-499c-8882-44398c857dc8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
