You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Tirthankar Chatterjee <tc...@commvault.com> on 2016/04/22 04:29:45 UTC
Solr5.5:DocValues/CopyField does not work with Atomic updates
Hi,
Here is the scenario for SOLR5.5:
FieldA type=<some date> stored=true indexed=true
FieldB type=<Date> stored=false indexed=true docValue=true usedocvalueasstored=false
FieldA copyTo FieldB
Try an Atomic update and we are getting this error:
possible analysis error: DocValuesField "mtmround" appears more than once in this document (only one value is allowed per field)
How do we resolve this.
***************************Legal Disclaimer***************************
"This communication may contain confidential and privileged material for the
sole use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message by mistake,
please advise the sender by reply email and delete the message. Thank you."
**********************************************************************
Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
Posted by Nick Vasilyev <ni...@gmail.com>.
I am also running into this problem on Solr 6.
On Sun, Apr 24, 2016 at 6:10 PM, Karthik Ramachandran <
kramachandran@commvault.com> wrote:
> I have opened JIRA
>
> https://issues.apache.org/jira/browse/SOLR-9034
>
> I will upload the patch soon.
>
> With Thanks & Regards
> Karthik Ramachandran
> CommVault
> Direct: (732) 923-2197
> Please don't print this e-mail unless you really need to
>
> -----Original Message-----
> From: Erick Erickson [mailto:erickerickson@gmail.com]
> Sent: Friday, April 22, 2016 8:24 PM
> To: solr-user <so...@lucene.apache.org>
> Subject: Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
>
> I think I just added the right person, let us know if you don't have
> access and/or if you need access to the LUCENE JIRA.
>
> Erick
>
> On Fri, Apr 22, 2016 at 5:17 PM, Karthik Ramachandran <
> kramachandran@commvault.com> wrote:
> > Eric
> > I have created a JIRA id (kramachandran@commvault.com). Once I get
> > access I will create the JIRA and submit the patch.
> >
> > With Thanks & Regards
> > Karthik Ramachandran
> > CommVault
> > Direct: (732) 923-2197
> > P Please don't print this e-mail unless you really need to
> >
> >
> >
> > On 4/22/16, 8:04 PM, "Erick Erickson" <er...@gmail.com> wrote:
> >
> >>Karthik:
> >>
> >>The Apache mailing list is pretty aggressive about removing
> >>attachments. Could you possibly open a JIRA and attach the file as a
> >>patch? If at all possible a patch file with just the diffs would be
> >>best.
> >>
> >>One problem is that it'll be a two-step process. The JIRAs have been
> >>being hit with spam, so you'll have to request access once you create
> >>a JIRA ID (this list would be fine).
> >>
> >>Best,
> >>Erick
> >>
> >>On Thu, Apr 21, 2016 at 9:09 PM, Karthik Ramachandran
> >><kr...@commvault.com> wrote:
> >>> We feel the issue is in
> >>>RealTimeGetComponent.getInputDocument(SolrCore
> >>>core,
> >>> BytesRef idBytes) where solr calls getNonStoredDVs and add the
> >>>fields to the original document without excluding the copyFields.
> >>>
> >>>
> >>>
> >>> We made changes to send the filteredList to
> >>>searcher.decorateDocValueFields
> >>> and it started working.
> >>>
> >>>
> >>>
> >>> Attached is the modified file.
> >>>
> >>>
> >>>
> >>> With Thanks & Regards
> >>> Karthik Ramachandran
> >>> CommVault
> >>> P Please don't print this e-mail unless you really need to
> >>>
> >>>
> >>>
> >>> -----Original Message-----
> >>> From: Karthik Ramachandran [mailto:mrktve@gmail.com]
> >>> Sent: Friday, April 22, 2016 12:08 AM
> >>> To: solr-user@lucene.apache.org
> >>> Subject: Re: Solr5.5:DocValues/CopyField does not work with Atomic
> >>>updates
> >>>
> >>>
> >>>
> >>> We are trying to update Field A.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> -Karthik
> >>>
> >>>
> >>>
> >>> On Thu, Apr 21, 2016 at 10:36 PM, John Bickerstaff
> >>><john@johnbickerstaff.com
> >>>
> >>>> wrote:
> >>>
> >>>
> >>>
> >>>> Which field do you try to atomically update? A or B or some other?
> >>>
> >>>> On Apr 21, 2016 8:29 PM, "Tirthankar Chatterjee" <
> >>>
> >>>> tchatterjee@commvault.com>
> >>>
> >>>> wrote:
> >>>
> >>>>
> >>>
> >>>> > Hi,
> >>>
> >>>> > Here is the scenario for SOLR5.5:
> >>>
> >>>> >
> >>>
> >>>> > FieldA type=<some date> stored=true indexed=true
> >>>
> >>>> >
> >>>
> >>>> > FieldB type=<Date> stored=false indexed=true docValue=true
> >>>
> >>>> > usedocvalueasstored=false
> >>>
> >>>> >
> >>>
> >>>> > FieldA copyTo FieldB
> >>>
> >>>> >
> >>>
> >>>> > Try an Atomic update and we are getting this error:
> >>>
> >>>> >
> >>>
> >>>> > possible analysis error: DocValuesField "mtmround" appears more
> >>>> > than
> >>>
> >>>> > once in this document (only one value is allowed per field)
> >>>
> >>>> >
> >>>
> >>>> > How do we resolve this.
> >>>
> >>>> >
> >>>
> >>>> >
> >>>
> >>>> >
> >>>
> >>>> > ***************************Legal
> >>>
> >>>> > Disclaimer***************************
> >>>
> >>>> > "This communication may contain confidential and privileged
> >>>> > material
> >>>
> >>>> > for the sole use of the intended recipient. Any unauthorized
> >>>> > review,
> >>>
> >>>> > use or distribution by others is strictly prohibited. If you have
> >>>
> >>>> > received the message by mistake, please advise the sender by
> >>>> > reply
> >>>
> >>>> > email and delete the message. Thank
> >>>
> >>>> you."
> >>>
> >>>> > *****************************************************************
> >>>> > ***
> >>>
> >>>> > **
> >>>
> >>>>
> >>>
> >>> ***************************Legal
> >>>Disclaimer***************************
> >>> "This communication may contain confidential and privileged material
> >>>for the sole use of the intended recipient. Any unauthorized review,
> >>>use or distribution by others is strictly prohibited. If you have
> >>>received the message by mistake, please advise the sender by reply
> >>>email and delete the message. Thank you."
> >>>
> >>>*********************************************************************
> >>>*
> >>
> >
> >
> >
> >
> > ***************************Legal Disclaimer***************************
> > "This communication may contain confidential and privileged material
> > for the sole use of the intended recipient. Any unauthorized review,
> > use or distribution by others is strictly prohibited. If you have
> > received the message by mistake, please advise the sender by reply email
> and delete the message. Thank you."
> > **********************************************************************
>
>
>
>
> ***************************Legal Disclaimer***************************
> "This communication may contain confidential and privileged material for
> the
> sole use of the intended recipient. Any unauthorized review, use or
> distribution
> by others is strictly prohibited. If you have received the message by
> mistake,
> please advise the sender by reply email and delete the message. Thank you."
> **********************************************************************
>
RE: Solr5.5:DocValues/CopyField does not work with Atomic updates
Posted by Karthik Ramachandran <kr...@commvault.com>.
I have opened JIRA
https://issues.apache.org/jira/browse/SOLR-9034
I will upload the patch soon.
With Thanks & Regards
Karthik Ramachandran
CommVault
Direct: (732) 923-2197
Please don't print this e-mail unless you really need to
-----Original Message-----
From: Erick Erickson [mailto:erickerickson@gmail.com]
Sent: Friday, April 22, 2016 8:24 PM
To: solr-user <so...@lucene.apache.org>
Subject: Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
I think I just added the right person, let us know if you don't have access and/or if you need access to the LUCENE JIRA.
Erick
On Fri, Apr 22, 2016 at 5:17 PM, Karthik Ramachandran <kr...@commvault.com> wrote:
> Eric
> I have created a JIRA id (kramachandran@commvault.com). Once I get
> access I will create the JIRA and submit the patch.
>
> With Thanks & Regards
> Karthik Ramachandran
> CommVault
> Direct: (732) 923-2197
> P Please don't print this e-mail unless you really need to
>
>
>
> On 4/22/16, 8:04 PM, "Erick Erickson" <er...@gmail.com> wrote:
>
>>Karthik:
>>
>>The Apache mailing list is pretty aggressive about removing
>>attachments. Could you possibly open a JIRA and attach the file as a
>>patch? If at all possible a patch file with just the diffs would be
>>best.
>>
>>One problem is that it'll be a two-step process. The JIRAs have been
>>being hit with spam, so you'll have to request access once you create
>>a JIRA ID (this list would be fine).
>>
>>Best,
>>Erick
>>
>>On Thu, Apr 21, 2016 at 9:09 PM, Karthik Ramachandran
>><kr...@commvault.com> wrote:
>>> We feel the issue is in
>>>RealTimeGetComponent.getInputDocument(SolrCore
>>>core,
>>> BytesRef idBytes) where solr calls getNonStoredDVs and add the
>>>fields to the original document without excluding the copyFields.
>>>
>>>
>>>
>>> We made changes to send the filteredList to
>>>searcher.decorateDocValueFields
>>> and it started working.
>>>
>>>
>>>
>>> Attached is the modified file.
>>>
>>>
>>>
>>> With Thanks & Regards
>>> Karthik Ramachandran
>>> CommVault
>>> P Please don't print this e-mail unless you really need to
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Karthik Ramachandran [mailto:mrktve@gmail.com]
>>> Sent: Friday, April 22, 2016 12:08 AM
>>> To: solr-user@lucene.apache.org
>>> Subject: Re: Solr5.5:DocValues/CopyField does not work with Atomic
>>>updates
>>>
>>>
>>>
>>> We are trying to update Field A.
>>>
>>>
>>>
>>>
>>>
>>> -Karthik
>>>
>>>
>>>
>>> On Thu, Apr 21, 2016 at 10:36 PM, John Bickerstaff
>>><john@johnbickerstaff.com
>>>
>>>> wrote:
>>>
>>>
>>>
>>>> Which field do you try to atomically update? A or B or some other?
>>>
>>>> On Apr 21, 2016 8:29 PM, "Tirthankar Chatterjee" <
>>>
>>>> tchatterjee@commvault.com>
>>>
>>>> wrote:
>>>
>>>>
>>>
>>>> > Hi,
>>>
>>>> > Here is the scenario for SOLR5.5:
>>>
>>>> >
>>>
>>>> > FieldA type=<some date> stored=true indexed=true
>>>
>>>> >
>>>
>>>> > FieldB type=<Date> stored=false indexed=true docValue=true
>>>
>>>> > usedocvalueasstored=false
>>>
>>>> >
>>>
>>>> > FieldA copyTo FieldB
>>>
>>>> >
>>>
>>>> > Try an Atomic update and we are getting this error:
>>>
>>>> >
>>>
>>>> > possible analysis error: DocValuesField "mtmround" appears more
>>>> > than
>>>
>>>> > once in this document (only one value is allowed per field)
>>>
>>>> >
>>>
>>>> > How do we resolve this.
>>>
>>>> >
>>>
>>>> >
>>>
>>>> >
>>>
>>>> > ***************************Legal
>>>
>>>> > Disclaimer***************************
>>>
>>>> > "This communication may contain confidential and privileged
>>>> > material
>>>
>>>> > for the sole use of the intended recipient. Any unauthorized
>>>> > review,
>>>
>>>> > use or distribution by others is strictly prohibited. If you have
>>>
>>>> > received the message by mistake, please advise the sender by
>>>> > reply
>>>
>>>> > email and delete the message. Thank
>>>
>>>> you."
>>>
>>>> > *****************************************************************
>>>> > ***
>>>
>>>> > **
>>>
>>>>
>>>
>>> ***************************Legal
>>>Disclaimer***************************
>>> "This communication may contain confidential and privileged material
>>>for the sole use of the intended recipient. Any unauthorized review,
>>>use or distribution by others is strictly prohibited. If you have
>>>received the message by mistake, please advise the sender by reply
>>>email and delete the message. Thank you."
>>>
>>>*********************************************************************
>>>*
>>
>
>
>
>
> ***************************Legal Disclaimer***************************
> "This communication may contain confidential and privileged material
> for the sole use of the intended recipient. Any unauthorized review,
> use or distribution by others is strictly prohibited. If you have
> received the message by mistake, please advise the sender by reply email and delete the message. Thank you."
> **********************************************************************
***************************Legal Disclaimer***************************
"This communication may contain confidential and privileged material for the
sole use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message by mistake,
please advise the sender by reply email and delete the message. Thank you."
**********************************************************************
Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
Posted by Erick Erickson <er...@gmail.com>.
I think I just added the right person, let us know if you don't have
access and/or if you need access to the LUCENE JIRA.
Erick
On Fri, Apr 22, 2016 at 5:17 PM, Karthik Ramachandran
<kr...@commvault.com> wrote:
> Eric
> I have created a JIRA id (kramachandran@commvault.com). Once I get
> access I will create the JIRA and submit the patch.
>
> With Thanks & Regards
> Karthik Ramachandran
> CommVault
> Direct: (732) 923-2197
> P Please don't print this e-mail unless you really need to
>
>
>
> On 4/22/16, 8:04 PM, "Erick Erickson" <er...@gmail.com> wrote:
>
>>Karthik:
>>
>>The Apache mailing list is pretty aggressive about removing
>>attachments. Could you possibly open a JIRA and attach the file as a
>>patch? If at all possible a patch file with just the diffs would be
>>best.
>>
>>One problem is that it'll be a two-step process. The JIRAs have been
>>being hit with spam, so you'll have to request access once you create
>>a JIRA ID (this list would be fine).
>>
>>Best,
>>Erick
>>
>>On Thu, Apr 21, 2016 at 9:09 PM, Karthik Ramachandran
>><kr...@commvault.com> wrote:
>>> We feel the issue is in RealTimeGetComponent.getInputDocument(SolrCore
>>>core,
>>> BytesRef idBytes) where solr calls getNonStoredDVs and add the fields
>>>to the
>>> original document without excluding the copyFields.
>>>
>>>
>>>
>>> We made changes to send the filteredList to
>>>searcher.decorateDocValueFields
>>> and it started working.
>>>
>>>
>>>
>>> Attached is the modified file.
>>>
>>>
>>>
>>> With Thanks & Regards
>>> Karthik Ramachandran
>>> CommVault
>>> P Please don't print this e-mail unless you really need to
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: Karthik Ramachandran [mailto:mrktve@gmail.com]
>>> Sent: Friday, April 22, 2016 12:08 AM
>>> To: solr-user@lucene.apache.org
>>> Subject: Re: Solr5.5:DocValues/CopyField does not work with Atomic
>>>updates
>>>
>>>
>>>
>>> We are trying to update Field A.
>>>
>>>
>>>
>>>
>>>
>>> -Karthik
>>>
>>>
>>>
>>> On Thu, Apr 21, 2016 at 10:36 PM, John Bickerstaff
>>><john@johnbickerstaff.com
>>>
>>>> wrote:
>>>
>>>
>>>
>>>> Which field do you try to atomically update? A or B or some other?
>>>
>>>> On Apr 21, 2016 8:29 PM, "Tirthankar Chatterjee" <
>>>
>>>> tchatterjee@commvault.com>
>>>
>>>> wrote:
>>>
>>>>
>>>
>>>> > Hi,
>>>
>>>> > Here is the scenario for SOLR5.5:
>>>
>>>> >
>>>
>>>> > FieldA type=<some date> stored=true indexed=true
>>>
>>>> >
>>>
>>>> > FieldB type=<Date> stored=false indexed=true docValue=true
>>>
>>>> > usedocvalueasstored=false
>>>
>>>> >
>>>
>>>> > FieldA copyTo FieldB
>>>
>>>> >
>>>
>>>> > Try an Atomic update and we are getting this error:
>>>
>>>> >
>>>
>>>> > possible analysis error: DocValuesField "mtmround" appears more than
>>>
>>>> > once in this document (only one value is allowed per field)
>>>
>>>> >
>>>
>>>> > How do we resolve this.
>>>
>>>> >
>>>
>>>> >
>>>
>>>> >
>>>
>>>> > ***************************Legal
>>>
>>>> > Disclaimer***************************
>>>
>>>> > "This communication may contain confidential and privileged material
>>>
>>>> > for the sole use of the intended recipient. Any unauthorized review,
>>>
>>>> > use or distribution by others is strictly prohibited. If you have
>>>
>>>> > received the message by mistake, please advise the sender by reply
>>>
>>>> > email and delete the message. Thank
>>>
>>>> you."
>>>
>>>> > ********************************************************************
>>>
>>>> > **
>>>
>>>>
>>>
>>> ***************************Legal Disclaimer***************************
>>> "This communication may contain confidential and privileged material
>>>for the
>>> sole use of the intended recipient. Any unauthorized review, use or
>>> distribution
>>> by others is strictly prohibited. If you have received the message by
>>> mistake,
>>> please advise the sender by reply email and delete the message. Thank
>>>you."
>>> **********************************************************************
>>
>
>
>
>
> ***************************Legal Disclaimer***************************
> "This communication may contain confidential and privileged material for the
> sole use of the intended recipient. Any unauthorized review, use or distribution
> by others is strictly prohibited. If you have received the message by mistake,
> please advise the sender by reply email and delete the message. Thank you."
> **********************************************************************
Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
Posted by Karthik Ramachandran <kr...@commvault.com>.
Eric
I have created a JIRA id (kramachandran@commvault.com). Once I get
access I will create the JIRA and submit the patch.
With Thanks & Regards
Karthik Ramachandran
CommVault
Direct: (732) 923-2197
P Please don't print this e-mail unless you really need to
On 4/22/16, 8:04 PM, "Erick Erickson" <er...@gmail.com> wrote:
>Karthik:
>
>The Apache mailing list is pretty aggressive about removing
>attachments. Could you possibly open a JIRA and attach the file as a
>patch? If at all possible a patch file with just the diffs would be
>best.
>
>One problem is that it'll be a two-step process. The JIRAs have been
>being hit with spam, so you'll have to request access once you create
>a JIRA ID (this list would be fine).
>
>Best,
>Erick
>
>On Thu, Apr 21, 2016 at 9:09 PM, Karthik Ramachandran
><kr...@commvault.com> wrote:
>> We feel the issue is in RealTimeGetComponent.getInputDocument(SolrCore
>>core,
>> BytesRef idBytes) where solr calls getNonStoredDVs and add the fields
>>to the
>> original document without excluding the copyFields.
>>
>>
>>
>> We made changes to send the filteredList to
>>searcher.decorateDocValueFields
>> and it started working.
>>
>>
>>
>> Attached is the modified file.
>>
>>
>>
>> With Thanks & Regards
>> Karthik Ramachandran
>> CommVault
>> P Please don't print this e-mail unless you really need to
>>
>>
>>
>> -----Original Message-----
>> From: Karthik Ramachandran [mailto:mrktve@gmail.com]
>> Sent: Friday, April 22, 2016 12:08 AM
>> To: solr-user@lucene.apache.org
>> Subject: Re: Solr5.5:DocValues/CopyField does not work with Atomic
>>updates
>>
>>
>>
>> We are trying to update Field A.
>>
>>
>>
>>
>>
>> -Karthik
>>
>>
>>
>> On Thu, Apr 21, 2016 at 10:36 PM, John Bickerstaff
>><john@johnbickerstaff.com
>>
>>> wrote:
>>
>>
>>
>>> Which field do you try to atomically update? A or B or some other?
>>
>>> On Apr 21, 2016 8:29 PM, "Tirthankar Chatterjee" <
>>
>>> tchatterjee@commvault.com>
>>
>>> wrote:
>>
>>>
>>
>>> > Hi,
>>
>>> > Here is the scenario for SOLR5.5:
>>
>>> >
>>
>>> > FieldA type=<some date> stored=true indexed=true
>>
>>> >
>>
>>> > FieldB type=<Date> stored=false indexed=true docValue=true
>>
>>> > usedocvalueasstored=false
>>
>>> >
>>
>>> > FieldA copyTo FieldB
>>
>>> >
>>
>>> > Try an Atomic update and we are getting this error:
>>
>>> >
>>
>>> > possible analysis error: DocValuesField "mtmround" appears more than
>>
>>> > once in this document (only one value is allowed per field)
>>
>>> >
>>
>>> > How do we resolve this.
>>
>>> >
>>
>>> >
>>
>>> >
>>
>>> > ***************************Legal
>>
>>> > Disclaimer***************************
>>
>>> > "This communication may contain confidential and privileged material
>>
>>> > for the sole use of the intended recipient. Any unauthorized review,
>>
>>> > use or distribution by others is strictly prohibited. If you have
>>
>>> > received the message by mistake, please advise the sender by reply
>>
>>> > email and delete the message. Thank
>>
>>> you."
>>
>>> > ********************************************************************
>>
>>> > **
>>
>>>
>>
>> ***************************Legal Disclaimer***************************
>> "This communication may contain confidential and privileged material
>>for the
>> sole use of the intended recipient. Any unauthorized review, use or
>> distribution
>> by others is strictly prohibited. If you have received the message by
>> mistake,
>> please advise the sender by reply email and delete the message. Thank
>>you."
>> **********************************************************************
>
***************************Legal Disclaimer***************************
"This communication may contain confidential and privileged material for the
sole use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message by mistake,
please advise the sender by reply email and delete the message. Thank you."
**********************************************************************
Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
Posted by Erick Erickson <er...@gmail.com>.
Karthik:
The Apache mailing list is pretty aggressive about removing
attachments. Could you possibly open a JIRA and attach the file as a
patch? If at all possible a patch file with just the diffs would be
best.
One problem is that it'll be a two-step process. The JIRAs have been
being hit with spam, so you'll have to request access once you create
a JIRA ID (this list would be fine).
Best,
Erick
On Thu, Apr 21, 2016 at 9:09 PM, Karthik Ramachandran
<kr...@commvault.com> wrote:
> We feel the issue is in RealTimeGetComponent.getInputDocument(SolrCore core,
> BytesRef idBytes) where solr calls getNonStoredDVs and add the fields to the
> original document without excluding the copyFields.
>
>
>
> We made changes to send the filteredList to searcher.decorateDocValueFields
> and it started working.
>
>
>
> Attached is the modified file.
>
>
>
> With Thanks & Regards
> Karthik Ramachandran
> CommVault
> P Please don't print this e-mail unless you really need to
>
>
>
> -----Original Message-----
> From: Karthik Ramachandran [mailto:mrktve@gmail.com]
> Sent: Friday, April 22, 2016 12:08 AM
> To: solr-user@lucene.apache.org
> Subject: Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
>
>
>
> We are trying to update Field A.
>
>
>
>
>
> -Karthik
>
>
>
> On Thu, Apr 21, 2016 at 10:36 PM, John Bickerstaff <john@johnbickerstaff.com
>
>> wrote:
>
>
>
>> Which field do you try to atomically update? A or B or some other?
>
>> On Apr 21, 2016 8:29 PM, "Tirthankar Chatterjee" <
>
>> tchatterjee@commvault.com>
>
>> wrote:
>
>>
>
>> > Hi,
>
>> > Here is the scenario for SOLR5.5:
>
>> >
>
>> > FieldA type=<some date> stored=true indexed=true
>
>> >
>
>> > FieldB type=<Date> stored=false indexed=true docValue=true
>
>> > usedocvalueasstored=false
>
>> >
>
>> > FieldA copyTo FieldB
>
>> >
>
>> > Try an Atomic update and we are getting this error:
>
>> >
>
>> > possible analysis error: DocValuesField "mtmround" appears more than
>
>> > once in this document (only one value is allowed per field)
>
>> >
>
>> > How do we resolve this.
>
>> >
>
>> >
>
>> >
>
>> > ***************************Legal
>
>> > Disclaimer***************************
>
>> > "This communication may contain confidential and privileged material
>
>> > for the sole use of the intended recipient. Any unauthorized review,
>
>> > use or distribution by others is strictly prohibited. If you have
>
>> > received the message by mistake, please advise the sender by reply
>
>> > email and delete the message. Thank
>
>> you."
>
>> > ********************************************************************
>
>> > **
>
>>
>
> ***************************Legal Disclaimer***************************
> "This communication may contain confidential and privileged material for the
> sole use of the intended recipient. Any unauthorized review, use or
> distribution
> by others is strictly prohibited. If you have received the message by
> mistake,
> please advise the sender by reply email and delete the message. Thank you."
> **********************************************************************
RE: Solr5.5:DocValues/CopyField does not work with Atomic updates
Posted by Karthik Ramachandran <kr...@commvault.com>.
We feel the issue is in RealTimeGetComponent.getInputDocument(SolrCore core, BytesRef idBytes) where solr calls getNonStoredDVs and add the fields to the original document without excluding the copyFields.
We made changes to send the filteredList to searcher.decorateDocValueFields and it started working.
Attached is the modified file.
With Thanks & Regards
Karthik Ramachandran
CommVault
P Please don't print this e-mail unless you really need to
-----Original Message-----
From: Karthik Ramachandran [mailto:mrktve@gmail.com]
Sent: Friday, April 22, 2016 12:08 AM
To: solr-user@lucene.apache.org
Subject: Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
We are trying to update Field A.
-Karthik
On Thu, Apr 21, 2016 at 10:36 PM, John Bickerstaff <john@johnbickerstaff.com
> wrote:
> Which field do you try to atomically update? A or B or some other?
> On Apr 21, 2016 8:29 PM, "Tirthankar Chatterjee" <
> tchatterjee@commvault.com<ma...@commvault.com>>
> wrote:
>
> > Hi,
> > Here is the scenario for SOLR5.5:
> >
> > FieldA type=<some date> stored=true indexed=true
> >
> > FieldB type=<Date> stored=false indexed=true docValue=true
> > usedocvalueasstored=false
> >
> > FieldA copyTo FieldB
> >
> > Try an Atomic update and we are getting this error:
> >
> > possible analysis error: DocValuesField "mtmround" appears more than
> > once in this document (only one value is allowed per field)
> >
> > How do we resolve this.
> >
> >
> >
> > ***************************Legal
> > Disclaimer***************************
> > "This communication may contain confidential and privileged material
> > for the sole use of the intended recipient. Any unauthorized review,
> > use or distribution by others is strictly prohibited. If you have
> > received the message by mistake, please advise the sender by reply
> > email and delete the message. Thank
> you."
> > ********************************************************************
> > **
>
***************************Legal Disclaimer***************************
"This communication may contain confidential and privileged material for the
sole use of the intended recipient. Any unauthorized review, use or distribution
by others is strictly prohibited. If you have received the message by mistake,
please advise the sender by reply email and delete the message. Thank you."
**********************************************************************
Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
Posted by Karthik Ramachandran <mr...@gmail.com>.
We are trying to update Field A.
-Karthik
On Thu, Apr 21, 2016 at 10:36 PM, John Bickerstaff <john@johnbickerstaff.com
> wrote:
> Which field do you try to atomically update? A or B or some other?
> On Apr 21, 2016 8:29 PM, "Tirthankar Chatterjee" <
> tchatterjee@commvault.com>
> wrote:
>
> > Hi,
> > Here is the scenario for SOLR5.5:
> >
> > FieldA type=<some date> stored=true indexed=true
> >
> > FieldB type=<Date> stored=false indexed=true docValue=true
> > usedocvalueasstored=false
> >
> > FieldA copyTo FieldB
> >
> > Try an Atomic update and we are getting this error:
> >
> > possible analysis error: DocValuesField "mtmround" appears more than once
> > in this document (only one value is allowed per field)
> >
> > How do we resolve this.
> >
> >
> >
> > ***************************Legal Disclaimer***************************
> > "This communication may contain confidential and privileged material for
> > the
> > sole use of the intended recipient. Any unauthorized review, use or
> > distribution
> > by others is strictly prohibited. If you have received the message by
> > mistake,
> > please advise the sender by reply email and delete the message. Thank
> you."
> > **********************************************************************
>
Re: Solr5.5:DocValues/CopyField does not work with Atomic updates
Posted by John Bickerstaff <jo...@johnbickerstaff.com>.
Which field do you try to atomically update? A or B or some other?
On Apr 21, 2016 8:29 PM, "Tirthankar Chatterjee" <tc...@commvault.com>
wrote:
> Hi,
> Here is the scenario for SOLR5.5:
>
> FieldA type=<some date> stored=true indexed=true
>
> FieldB type=<Date> stored=false indexed=true docValue=true
> usedocvalueasstored=false
>
> FieldA copyTo FieldB
>
> Try an Atomic update and we are getting this error:
>
> possible analysis error: DocValuesField "mtmround" appears more than once
> in this document (only one value is allowed per field)
>
> How do we resolve this.
>
>
>
> ***************************Legal Disclaimer***************************
> "This communication may contain confidential and privileged material for
> the
> sole use of the intended recipient. Any unauthorized review, use or
> distribution
> by others is strictly prohibited. If you have received the message by
> mistake,
> please advise the sender by reply email and delete the message. Thank you."
> **********************************************************************