: 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&#
red using string instead?
Tim
-Original Message-
From: Christopher Baird [mailto:cba...@cardinalcommerce.com]
Sent: Tuesday, September 01, 2009 7:30 AM
To: solr-user@lucene.apache.org
Subject: Adding new docs, but duplicating instead of updating
Hi All,
I'm running Solr in a multicore setup.
Hi All,
I'm running Solr in a multicore setup. I've set one of the cores to have a
specific field as the unique key (marked as the uniqueKey in the document
and the field is defined as required). I'm sending an command with
all the docs using a multipart post. After running the add file, I
