Thanks Eric and Shawn, appreciate your help.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Indexing-question-on-individual-field-update-tp4116605p4116831.html
Sent from the Solr - User mailing list archive at Nabble.com.
Update and add are basically the same thing if there's an existing document.
There will be some performance consequence since you're getting the stored
fields on the server as opposed to getting the full input from the external
source
and handing it to Solr. However, I know of at least one situatio
On 2/11/2014 2:37 PM, shamik wrote:
Eric,
Thanks for your reply. I should have given a better context. I'm currently
running an incremental crawl daily on this particular source and indexing
the documents. Incremental crawl looks for any change since last crawl date
based on the document publ
Ok, I was wrong here. I can always set the indextimestamp field with current
time (NOW) for every atomic update. On a similar note, is there any
performance constraint with updates compared to add ?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Indexing-question-on
he
fact that I can't remove stale content.
Let me know if I'm missing something here.
- Thanks,
Shamik
--
View this message in context:
http://lucene.472066.n3.nabble.com/Indexing-question-on-individual-field-update-tp4116605p4116757.html
Sent from the Solr - User mailing list archive at Nabble.com.
I'm assuming you're using the atomic update feature to
update the individual field, why not use it when you replace
the rest of the doc?
Best,
Erick
On Mon, Feb 10, 2014 at 5:20 PM, Shamik Bandopadhyay wrote:
> Hi,
>
> I'm currently indexing a bunch of fields for a given document. For e.g.
>
Hi,
I'm currently indexing a bunch of fields for a given document. For e.g.
let's assume there's a field called "rating". The rating field is not part
of the original document during index, so the value is blank. The field
gets updated by an external service when the document is rated by users.
