Hi Chetan, The overall approach looks ok.
Some questions about indexing. How will you deal with JVM failure ? and related. How frequently will commits to the persisted index be performed ? I assume that switching to use ElasticSearch, which delivers NRT reliably in the 0.1s range has been rejected as an option ? If it has, you may find yourself implementing much of the core of ElasticSearch to make NTR work properly in a cluster. Best Regards Ian On 24 July 2015 at 08:09, Chetan Mehrotra <[email protected]> wrote: > On Fri, Jul 24, 2015 at 12:15 PM, Michael Marth <[email protected]> wrote: > > From your description I am not sure how the indexing would be triggered > for local changes. Probably not through the Async Indexer (this would not > gain us much, right?). Would this be a Commit Hook? > > My thought was to use an Observor so as to not add cost to commit > call. Observor would listen only for local changes and would invoke > IndexUpdate on the diff > > Chetan Mehrotra >
