/content/support/en/documentation/cloudera-search/cloudera-search-documentation-v1-latest.html
> > -- see the user guide pdf, " update-conflict-resolver" parameter
> >
> > James
> >
> > -Original Message-----
> > From: anirudh...@gmail.com [mail
> Anirudha Jadhav
> Sent: Tuesday, June 11, 2013 10:47 AM
> To: solr-user@lucene.apache.org
> Subject: Re: index merge question
>
> From my experience the lucene mergeTool and the one invoked by coreAdmin is a
> pure lucene implementation and does not understand
ache.org
Subject: Re: index merge question
From my experience the lucene mergeTool and the one invoked by coreAdmin is a
pure lucene implementation and does not understand the concepts of a unique
Key(solr land concept)
http://wiki.apache.org/solr/MergingSolrIndexes has a cautionary not
>From my experience the lucene mergeTool and the one invoked by
coreAdmin is a pure lucene implementation and does not understand the
concepts of a unique Key(solr land concept)
http://wiki.apache.org/solr/MergingSolrIndexes has a cautionary note
at the end
we do frequent index merges for which
Yeah, you have to carefully manage things if you are map/reduce building
indexes *and* updating documents in other ways.
If your 'source' data for MR index building is the 'truth', you also have the
option of not doing incremental index merging, and you could simply rebuild the
whole thing eve
Thanks Mark. My question is stemming from the new cloudera search stuff.
My concern its that if while rebuilding the index someone updates a doc
that update could be lost from a solr perspective. I guess what would need
to happen to ensure the correct information was indexed would be to record
th
I have noticed that when I write a doc with an id that already exists, it
creates a new revision with the only the fields from the second write. I
guess there is a REST API in the latest solr version which updates only
selected fields.
In my opinion, merge should be creating a doc which is a union
On Jun 8, 2013, at 12:52 PM, Jamie Johnson wrote:
> When merging through the core admin (
> http://wiki.apache.org/solr/MergingSolrIndexes) what is the policy for
> conflicts during the merge? So for instance if I am merging core 1 and
> core 2 into core 0 (first example), what happens if core
