: specified (again, using schema browser). The unique key field is marked as
: type textTight.
your uniqueKey field needs to be something where everydoc is only going to
produce a single token, if you are using textTight, and sending product
sku type data (as mentioned in another mesg in this t
; cba...@cardinalcommerce.com
Subject: RE: Adding new docs, but duplicating instead of updating
What is the value of your uniqueKey?
-Original Message-
From: Christopher Baird [mailto:cba...@cardinalcommerce.com]
Sent: Tuesday, September 01, 2009 8:20 AM
To: solr-user@lucene.apache.org
Subjec
What is the value of your uniqueKey?
-Original Message-
From: Christopher Baird [mailto:cba...@cardinalcommerce.com]
Sent: Tuesday, September 01, 2009 8:20 AM
To: solr-user@lucene.apache.org
Subject: RE: Adding new docs, but duplicating instead of updating
Hi Tim,
I appreciate the
STEMS]
[mailto:timothy.j.har...@nasa.gov]
Sent: Tuesday, September 01, 2009 10:45 AM
To: solr-user@lucene.apache.org; cba...@cardinalcommerce.com
Subject: RE: Adding new docs, but duplicating instead of updating
I could be off base here, maybe using textTight as unique key is a common
SOLR practice I don&#
I could be off base here, maybe using textTight as unique key is a common SOLR
practice I don't know. But, It would seem to me that using any field type that
transforms a value (even if it is just whitespace removal) could be
problematic. Maybe not the source of your issue here, but I'd be wo
