Depends on your goal here. I'm guessing you're using
atomic updates, in which case you need to use "set"
rather than "add" as the former replaces the contents.
See: http://wiki.apache.org/solr/UpdateJSON#Solr_4.0_Example
If you're simply re-indexing the documents, just send the entire
fresh document to solr and it'll replace the earlier document
completely.
Best
Erick
On Mon, May 6, 2013 at 4:14 AM, Nikhil Kumar <nikhil.ku...@hashedin.com> wrote:
> Hey,
> I have recently started using solr, I have a list of users, which are
> subscribed to some lists.
> eg.
> user a[
> id:a
> liists[
> list_a
> ]
> ]
> user b[
> id:b
> liists[
> list_a
> ]
> ]
> I am using {"id": a, "lists":{"add":"list_a"}} to add particular list a
> user.
> but what is happening if I use the same command again, it again adds the
> same list, which i want to avoid.
> user a[
> id:a
> liists[
> list_a,
> list_a
> ]
> ]
> I searched the documentation and tutorials, i found
>
> -
>
> overwrite = "true" | "false" — default is "true", meaning newer
> documents will replace previously added documents with the same uniqueKey.
> -
>
> commitWithin = "(milliseconds)" if the "commitWithin" attribute is
> present, the document will be added within that time. [image: <!>]
> Solr1.4 <http://wiki.apache.org/solr/Solr1.4>. See
> CommitWithin<http://wiki.apache.org/solr/CommitWithin>
> -
>
> (deprecated) allowDups = "true" | "false" — default is "false"
> -
>
> (deprecated) overwritePending = "true" | "false" — default is negation
> of allowDups
> -
>
> (deprecated) overwriteCommitted = "true"|"false" — default is negation
> of allowDups
>
>
> but using overwrite and allowDups didn't solve the problem either, seems
> because there is no unique id but just value.
>
> So the question is how to solve this problem?
>
> --
> Thank You and Regards,
> Nikhil Kumar
> +91-9916343619
> Technical Analyst
> Hashed In Technologies Pvt. Ltd.
