Re: Changing indexed property on a field from false to true

2013-10-24 Thread Upayavira
When this gets interesting is if we had batch atomic updates. Imagine you could do indexCount++ fro all docs matching the query category:sport. Could be really useful. /dreaming. Upayavira On Thu, Oct 24, 2013, at 05:40 PM, Aloke Ghoshal wrote: > Upayavira - Nice idea pushing in a nominal update

Re: Changing indexed property on a field from false to true

2013-10-24 Thread Aloke Ghoshal
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,

Re: Changing indexed property on a field from false to true

2013-10-23 Thread michael.boom
I've made a test, based on your suggestion. Using the example in 4.5.0 i set the title field as indexed=false, indexed a couple of docs: 1 BigApple 2 SmallApple and made fq=title:BigApple. No docs were returned, of course. Then I modified the schema, setting indexed=true for the

Re: Changing indexed property on a field from false to true

2013-10-23 Thread Upayavira
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 upd