On Thu, Jun 6, 2013 at 1:52 PM, Jack Krupansky wrote:
> "read current state, manipulate fields and then add the document with the
> same id)"
>
> Ahh... then you have an IMPLICIT reference to the field in your Java code -
> you explicitly told Solr that you wanted to start with all existing field
ing to a multivalued field. And you need a simple (non-Map) value for
your ID field.
-- Jack Krupansky
-Original Message-
From: Robert Krüger
Sent: Thursday, June 06, 2013 7:25 AM
To: solr-user@lucene.apache.org
Subject: Re: copyField generates "multiple values encountered for non
multi
-Original Message-
From: Robert Krüger
Sent: Thursday, June 06, 2013 7:15 AM
To: solr-user@lucene.apache.org
Subject: Re: copyField generates "multiple values encountered for non
multiValued field"
On Wed, Jun 5, 2013 at 9:12 PM, Jack Krupansky
wrote:
Look in the Solr log - the err
I don't know what I have to do to use the atomic update feature but I
am not aware of using it. But the way you describe it, it means that
the copyField directive does not overwrite the existing field content
and that's an easy explanation to what is happening in my case. Then
the second update (wh
On Wed, Jun 5, 2013 at 9:12 PM, Jack Krupansky wrote:
> Look in the Solr log - the error message should tell you what the multiple
> values are. For example,
>
> 95484 [qtp2998209-11] ERROR org.apache.solr.core.SolrCore –
> org.apache.solr.common.SolrException: ERROR: [doc=doc-1] multiple values
: I updated the Index using SolrJ and got the exact same error message
there aren't a lot of specifics provided in this thread, so this may not
be applicable, but if you mean you actaully using the "atomic updates"
feature to update an existing document then the problem is that you still
have
-Original Message-
From: Robert Krüger
Sent: Wednesday, June 05, 2013 1:17 PM
To: solr-user@lucene.apache.org
Subject: Re: copyField generates "multiple values encountered for non
multiValued field"
OK, I have two fields defined as follows:
and this copyField dire
:37 AM
> To: solr-user@lucene.apache.org
> Subject: copyField generates "multiple values encountered for non
> multiValued field"
>
>
> I have the exact same problem as the guy here:
>
> http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201105.mbox/%3C3
:37 AM
To: solr-user@lucene.apache.org
Subject: copyField generates "multiple values encountered for non
multiValued field"
I have the exact same problem as the guy here:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201105.mbox/%3C3A2B3E42FCAA4BF496AE625426C5C6E4@Wurstsemmel%3E
AFAIC
I think the suggestion I have seen is that copyField should be
index-only and - therefore - will not be returned. It is primarily
there to make searching easier by aggregating fields or to provide
alternative analyzer pipeline.
Can you make your copyField destination not stored?
Regards,
Alex.
I have the exact same problem as the guy here:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201105.mbox/%3C3A2B3E42FCAA4BF496AE625426C5C6E4@Wurstsemmel%3E
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
: This is for debugging purposes, so I am sending the exact same data that are
: already stored in Solr's index.
...
: ERROR: [288400] multiple values encountered for non multiValued field
: "field2" [fieldvalue, fieldvalue]
:
: The scenario:
: - "field1" is implicitly single value, type
Alexander,
I saw the same behavior in 1.4.x with non-multivalued fields when
"updating" the document in the index (i.e obtaining the doc from the
index, modifying some fields and then adding the document with the same
id back). I do not know what causes this, but it looks like the
copyField logic
Dear list,
hope somebody can help me understand/avoid this.
I am sending an "add" request with allowDuplicates=false to a Solr 1.4.1
instance.
This is for debugging purposes, so I am sending the exact same data that are
already stored in Solr's index.
I am using the PHP PECL libraries, which f
14 matches
Mail list logo
