Hmmm, not sure that would work for diferent values? But it does point
the way to a different solution, write a custom update processor that
removed multivalued entries
FWIW,
Erick
On Thu, May 30, 2013 at 1:54 PM, Alexandre Rafalovitch
wrote:
> On Thu, May 30, 2013 at 1:03 PM, Iain Lopata wr
is just for reading the solr
configurations at startup, and it's been removed in recent versions
anyway so it's not surprising that didn't help.
This has been a "feature" of solr for some time, there's no good way
to say "just keep going". There was some work on this with SOLR-445,
but i tdied on
On Thu, May 30, 2013 at 1:03 PM, Iain Lopata wrote:
> For example, a document which has two address fields when
> my Solr schema.xml does not specify address as being multi-valued (and I do
> not want it to be).
No help on the core topic, but a workaround for the specific situation
could be:
ht
On 5/30/2013 11:03 AM, Iain Lopata wrote:
When indexing documents, I hit an occasional document that does not match
the Solr schema. For example, a document which has two address fields when
my Solr schema.xml does not specify address as being multi-valued (and I do
not want it to be). Ideally,
I am using Nutch 1.6 and Solr 1.4.1 on Ubuntu in local mode and using
Nutch's solrindex to index documents into Solr.
When indexing documents, I hit an occasional document that does not match
the Solr schema. For example, a document which has two address fields when
my Solr schema.xml does not
I am using Nutch 1.6 and Solr 1.4.1 on Ubuntu in local mode and using
Nutch's solrindex to index documents into Solr.
When indexing documents, I hit an occasional document that does not match
the Solr schema. For example, a document which has two address fields when
my Solr schema.xml does not
