27, 2017 4:07:19 AM
Subject: Re: Documents issue
I may be wrong and don't have time to check the code in details now, but I
would say you need to define the default in the destination field as well.
The copy field should take in input the plain content of the field ( which
is null) and then
Only change was rename to remove periods from the fieldnames
Sent from my iPhone
> On Jan 27, 2017, at 11:53 AM, alessandro.benedetti
> wrote:
>
> Hi Khris,
> can you paste here the diff between the OK status and the KO status ?
> Has only the name of the destination field changed ? ( a replac
Hi Khris,
can you paste here the diff between the OK status and the KO status ?
Has only the name of the destination field changed ? ( a replace of '.' with
'_' ?)
Do you have any dynamic field defined ?
Cheers
--
View this message in context:
http://lucene.472066.n3.nabble.com/How-to-alter-the
Why would this behavior changed from one day to the next? I ran crawl and index
several times with no issues, changed the schematic xml definition of a couple
of fields, ran crawl and index and produced the dataset with missing copyfields.
Sent from my iPhone
> On Jan 27, 2017, at 4:07 AM, ales
I may be wrong and don't have time to check the code in details now, but I
would say you need to define the default in the destination field as well.
The copy field should take in input the plain content of the field ( which
is null) and then pass that content to the destination field.
Properties
Running the latest crawl from Nutch to SOLR 5.4.1 it seems that my copy fields
do not work as expected anymore.
Why would copyField ignore the default all of a sudden?
I've not made any significant changes to SOLR and none at all to nutch.
{
"response":{"numFound":699,"start":0,"do
