indexing and it's horribly slow. 50GB would
>> take at least a day...maybe 2 and I obviously can't have a client down for
>> that long in Production, but if I did it on a backup SOLR box....copying
>> 50GB into place is much much quicker.
>>
>> -Original Messag
in the week though.
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Tuesday, March 7, 2017 11:05 AM
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: Getting an error: was indexed without position data;
cannot run PhraseQuery
First, it's not clear w
m]
> Sent: Monday, March 6, 2017 8:48 PM
> To: solr-user <solr-user@lucene.apache.org>
> Subject: Re: Getting an error: was indexed without position data;
> cannot run PhraseQuery
>
> You're in a pickle then. If you change the definition you need to re-index.
>
> But you cla
ck reply Erick!
>
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Monday, March 6, 2017 5:33 PM
> To: solr-user <solr-user@lucene.apache.org>
> Subject: Re: Getting an error: was indexed without position
> data; cannot ru
m: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Monday, March 6, 2017 5:33 PM
> To: solr-user <solr-user@lucene.apache.org>
> Subject: Re: Getting an error: was indexed without position data;
> cannot run PhraseQuery
>
> Usually an _s field is a "string" t
scratch. H
Thanks for the quick reply Erick!
-Original Message-
From: Erick Erickson [mailto:erickerick...@gmail.com]
Sent: Monday, March 6, 2017 5:33 PM
To: solr-user <solr-user@lucene.apache.org>
Subject: Re: Getting an error: was indexed without position data;
cann
Usually an _s field is a "string" type, so be sure you didn't change
the definition without completely re-indexing. In fact I generally
either index to a new collection or remove the data directory
entirely.
right, the field isn't indexed with position information. That
combined with (probably)
