erhead with this?
>
> Thanks,
> Srinivas
>
>
> From: Munendra S N
> Sent: 30 October 2020 19:20
> To: solr-user@lucene.apache.org
> Subject: Re: Avoiding duplicate entry for a multivalued field
>
> Srinivas,
>
> For atomic updates, you could use add-disti
Thanks Munendra, this will really help me. Are there any performance overhead
with this?
Thanks,
Srinivas
From: Munendra S N
Sent: 30 October 2020 19:20
To: solr-user@lucene.apache.org
Subject: Re: Avoiding duplicate entry for a multivalued field
Srinivas,
For atomic updates, you could use
g query time, the field returns only
> unique values? Am I right with my assumption?
> >
> > And also, what is the performance overhead for this UniqueFiled*Factory?
> >
> > Thanks,
> > Srinivas
> >
> > From: Dwane Hall
> > Sent: 29 October 2020 1
right with my assumption?
>
> And also, what is the performance overhead for this UniqueFiled*Factory?
>
> Thanks,
> Srinivas
>
> From: Dwane Hall
> Sent: 29 October 2020 14:33
> To: solr-user@lucene.apache.org
> Subject: Re: Avoiding duplicate entry for a multivalued fi
. May be during query time, the field returns only unique
> values? Am I right with my assumption?
>
> And also, what is the performance overhead for this UniqueFiled*Factory?
>
> Thanks,
> Srinivas
>
> From: Dwane Hall
> Sent: 29 October 2020 14:33
> To: solr-user@lucene
,
Srinivas
From: Dwane Hall
Sent: 29 October 2020 14:33
To: solr-user@lucene.apache.org
Subject: Re: Avoiding duplicate entry for a multivalued field
Srinivas this is possible by adding an unique field update processor to the
update processor chain you are using to perform your updates (/update,
/update
Srinivas this is possible by adding an unique field update processor to the
update processor chain you are using to perform your updates (/update,
/update/json, /update/json/docs, .../a_custom_one)
The Java Documents explain its use nicely
