Upayavira - Nice idea pushing in a nominal update when all fields are stored, and it does work. The nominal update could be sent to a boolean type dynamic field, that's not to be used for anything other than maybe identifying documents that are done re-indexing.
On Wed, Oct 23, 2013 at 7:47 PM, Upayavira <u...@odoko.co.uk> wrote: > The content needs to be re-indexed, the question is whether you can use > the info in the index to do it rather than pushing fresh copies of the > documents to the index. > > I've often wondered whether atomic updates could be used to handle this > sort of thing. If all fields are stored, push a nominal update to cause > the document to be re-indexed. I've never tried it though. I'd be > curious to know if it works. > > Upayavira > > On Wed, Oct 23, 2013, at 02:25 PM, michael.boom wrote: > > Being given > > <field name="title" type="string" <b>indexed="false"* stored="true" > > multiValued="false" /> > > Changed to > > <field name="title" type="string" <b>indexed="true"* stored="true" > > multiValued="false" /> > > > > Once the above is done and the collection reloaded, is there a way I can > > build that index on that field, without reindexing the everything? > > > > Thank you! > > > > > > > > ----- > > Thanks, > > Michael > > -- > > View this message in context: > > > http://lucene.472066.n3.nabble.com/Changing-indexed-property-on-a-field-from-false-to-true-tp4097213.html > > Sent from the Solr - User mailing list archive at Nabble.com. >
