Hi, I am also very much interested in this, since we use Solr 4 with NRT where we update index every second but most of time it update only stored filed. if Solr/Lucene could provide external datastore without re-indexing even for stored field only, it would be very beneficial for frequent update use case, where cache invalidation will not happen for stored fields update and it will improve indexing performance due to smaller index size.
Here is below link for similar work. http://www.flax.co.uk/blog/2012/06/22/updating-individual-fields-in-lucene-with-a-redis-backed-codec/ On Fri, Nov 23, 2012 at 11:42 AM, Simone Gianni <simo...@apache.org> wrote: > Posted, > see it here > > http://lucene.472066.n3.nabble.com/Possible-sharded-and-replicated-replacement-for-ExternalFileFields-in-SolrCloud-td4022108.html > > Simone > > > 2012/11/23 Simone Gianni <simo...@apache.org> > > > 2012/11/22 Martin Koch <m...@issuu.com> > > > >> IMO it would be ideal if the lucene/solr community could come up with a > >> good way of updating fields in a document without reindexing. This could > >> be > >> by linking to some external data store, or in the lucene/solr internals. > >> If > >> it would make things easier, a good first step would be to have > >> dynamically > >> updateable numerical fields only. > >> > > > > Hi Martin, > > I'm working on implementing exactly this, and I have a working prototype > > right now. I'm going to write on lucene dev about the details and asking > > advice there. I'll contribute the code, so anyone interested followup on > > dev. > > > > Simone > > > > >
