On 3/12/2015 3:36 PM, Alexandre Rafalovitch wrote:
Manual optimize is no longer needed for modern Solr. It does great
optimization automatically. The only reason I recommended it here is
to make sure that all segments are brought up to the latest version
and the deleted documents are purged.
Hi,
I've a field which is being used for result grouping. Here's the field
definition.
field name=ADDedup type=string indexed=true stored=true
multiValued=false required=false omitNorms=true docValues=true/
This started once I did a rolling update from 4.7 to 5.0. I started getting
the
On 3/11/2015 4:45 PM, shamik wrote:
field name=DocumentType type=string indexed=true stored=true
multiValued=false required=false omitNorms=true docValues=true
/ 3/11/2015, 2:14:30 PM ERROR SolrDispatchFilter
null:java.lang.IllegalStateException: unexpected docvalues type NONE
for field
Manual optimize is no longer needed for modern Solr. It does great
optimization automatically. The only reason I recommended it here is
to make sure that all segments are brought up to the latest version
and the deleted documents are purged. That's something that also would
happen automatically
Wow, optimize worked like a charm. This really addressed the docvalues
issue. A follow-up question, is it recommended to run optimize in a
Production Solr index ? Also, in a Sorl cloud mode, do we need to run
optimize on each instance / each shard / any instance ?
Appreciate your help Alex.
--
Do you have any really old segments in that index? Could be worth
trying to optimize them down to one in latest format first.
Like Shawn, this is just a one more idea proposal.
Regards,
Alex.
Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
http://www.solr-start.com/
On
Well, I think I've narrowed down the issue. The error is happening when I'm
trying to do a rolling update from Solr 4.7 (which is our current version)
to 5.0 . I'm able to re-produce this couple of times. If I do a fresh index
on a 5.0, it works. Not sure if there's any other way to mitigate it.
Looks like it's happening for any field which is using docvalues.
java.lang.IllegalStateException: unexpected docvalues type NONE for field
'title_sort' (expected=SORTED). Use UninvertingReader or index with
docvalues.
Any idea ?
--
View this message in context:
: unexpected docvalues type NONE
: on result grouping
:
: Hi,
:
:I've a field which is being used for result grouping. Here's the field
: definition.
:
: field name=ADDedup type=string indexed=true stored=true
: multiValued=false required=false omitNorms=true docValues=true/
:
: This started
Thanks for your reply. Initially, I was under the impression that the issue
is related to grouping as group queries were failing. Later, when I looked
further, I found that it's happening for any field for which the docvalue
has turned on. The second example I took was from another field. Here's a
10 matches
Mail list logo
