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 <kramachand...@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:mrk...@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 <j...@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" < > >> tchatter...@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." > **********************************************************************
