dated for 4.5 yet, but the gist of
the examples is the same.)
-- Jack Krupansky
-Original Message-
From: Jack Krupansky
Sent: Wednesday, October 30, 2013 9:03 AM
To: solr-user@lucene.apache.org
Subject: Re: Atomic Updates in SOLR
Unfortunately, atomic "add" is add to a "l
Unfortunately, atomic "add" is add to a "list" (append) rather than add to a
"set" (only unique values). But, you can use the unique fields update
processor (solr.UniqFieldsUpdateProcessorFactory) to de-dupe specified
multivalued fields.
See:
http://lucene.apache.org/solr/4_5_1/solr-core/org/a
Think it'll be a good thing to have.
I just created a JIRA for that.
https://issues.apache.org/jira/browse/SOLR-5403
Will try and get to it soon.
On Wed, Oct 30, 2013 at 4:28 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> Ah I misread your email. You are actually sending the updat
Ah I misread your email. You are actually sending the update twice and
asking about how to dedup the multi-valued field values.
No I don't think we have an update processor which can do that.
On Wed, Oct 30, 2013 at 4:18 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> Perhaps you a
I am not sure if optimistic concurrency would help in deduplicating but
yes, as Shalin points out, you'll be able to spot issues with your client
code.
On Wed, Oct 30, 2013 at 4:18 PM, Shalin Shekhar Mangar <
shalinman...@gmail.com> wrote:
> Perhaps you are running the update request more than
Perhaps you are running the update request more than once accidentally?
Can you try using optimistic update with _version_ while sending the
update? This way, if some part of your code is making a duplicate request
then Solr would throw an error.
See
https://cwiki.apache.org/confluence/display/so
