lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Krüger <>
Subject Re: copyField generates "multiple values encountered for non multiValued field"
Date Wed, 05 Jun 2013 17:17:07 GMT
OK, I have two fields defined as follows:

  <field name="name"   type="string"   indexed="true"  stored="true"
multiValued="false" />
  <field name="name2"   type="string_ci"   indexed="true"
stored="true"  multiValued="false" />

and this copyField directive

 <copyField source="name" dest="name2"/>

I updated the Index using SolrJ and got the exact same error message
that is in the subject. However, while waiting for feedback I built a
workaround at the application level and now reconstructing the
original state, to be able to answer you, I have different behaviour.
What happens now is that the field "name2" is populated with multiple
values although it is not defined as multiValued (see above).

Although this is strange, it is consistent with the earlier problem in
that copyField does not seem to overwrite the existing field values. I
may be using it incorrectly (it's the first time I am using copyField)
but the docs in the wiki did not say anything about an overwrite



On Wed, Jun 5, 2013 at 5:16 PM, Jack Krupansky <> wrote:
> Try describing your own symptom in your own words - because his issue
> related to Solr 1.4. I mean, where exactly are you setting
> "allowDuplicates=false"?? And why do you think it has anything to do with
> adding documents to Solr? Solr 1.4 did not have atomic update, so sending
> the exact same document twice would not result in a change in the index
> (unless you had a date field with a value of "NOW".) Copy field only uses
> values from the current document.
> -- Jack Krupansky
> -----Original Message----- From: Robert Krüger
> Sent: Wednesday, June 05, 2013 10:37 AM
> To:
> Subject: copyField generates "multiple values encountered for non
> multiValued field"
> I have the exact same problem as the guy here:
> AFAICS he did not get an answer. Is this a known issue? What can I do
> other than doing what copyField should do in my application?
> I am using solr 4.0.0.
> Thanks,
> Robert

View raw message