This JIRA is "complicated", don't really expect it in 4.9 as it's been hanging around for quite a while. Everyone would like this, but it's not easy.
Atomic updates will work, but you have to stored="true" for all source fields. Under the covers this actually reads the document out of the stored fields, deletes the old one and adds it over again. FWIW, Erick On Tue, Jul 1, 2014 at 5:32 AM, Sandeep Khanzode <sandeep_khanz...@yahoo.com.invalid> wrote: > Hi, > > I wanted to know of the best approach to follow if a few fields in my indexed > documents are changing at run time (after index and before or during search), > but a majority of them are created at index time. > > I could see the JIRA given below but it is scheduled for Lucene 4.9, I > believe. > > There are a few other approaches, like maintaining a separate index for > changing fields and use either a parallelreader or use a Join. > > Can everyone share their experience for this scenario on how it is handled in > your systems? Thanks, > > [LUCENE-4258] Incremental Field Updates through Stacked Segments - ASF JIRA > > > [LUCENE-4258] Incremental Field Updates through Stacked Segments - ASF JIRA > Shai and I would like to start working on the proposal to Incremental Field > Updates outlined here (http://markmail.org/message/zhrdxxpfk6qvdaex). > View on issues.apache.org Preview by Yahoo > > > ----------------------- > Thanks n Regards, > Sandeep Ramesh Khanzode --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
