Hi there, in the last couple of years we managed to customize Apache Lucene (through its public API) to support branching, tagging and compare in a concurrent fashion for our server application. We managed to achieve this by using a couple of custom Directory, exactly one IndexDeletionPolicy and one MergePolicy implementations. Currently we are considering to replace Lucene with Elasticsearch on the server-side. Before we jumped into the details of collecting the differences between the two technologies in respect of the search and indexing functionality and for instance how to port our custom collectors and how to replace NDVs, we would like to make sure if it is possible at all.
I've just checked out the source and realized that the registration of the services are done via various module implementations and the actual configured service implementations are injected into the constructors. For the sake of simplicity is there a way for example to create an Elasticsearch module which forces the underlying IndexWriter to use the FooCustomDeletionPolicy instead of the default KeepOnlyLastDeletionPolicy? I assume if this is straightforward we could use or custom implementations for the directory and the IndexWriter what we are currently using with pure Lucene. After doing some research I found this [1] thread. Am I close to the answer/solution? I have to notice we would like to achieve this without forking the public repository. Thanks in advance for the feedbacks. Cheers, Akos [1]: https://groups.google.com/forum/#!topic/elasticsearch/rFaLnI5FRf4 -- 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/0345efea-3134-488d-b13d-199a24642422%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
