Hi Shawn,
The listing_lastmodified field was not changed. I only added a new field. I
have removed the field, but I still get the error.
Thanks
Prashant
On Wed, Apr 12, 2017 at 11:20 PM, Shawn Heisey wrote:
> On 4/12/2017 8:04 PM, Prashant Saraswat wrote:
> > I'm using Solr 6.4.0. The schema w
On 4/12/2017 8:04 PM, Prashant Saraswat wrote:
> I'm using Solr 6.4.0. The schema was created on 6.4.0 and I indexed several
> hundred thousand documents and everything was fine.
>
> Now I added one field to the schema:
>
> stored="true" required="false"/>
>
> I suddenly start getting this error f
with this field ). See full
exception below.
Am I supposed to reindex the entire dataset when anything changes in the
schema as long as even one field is using docvalues?
Thanks
Prashant
java.lang.IllegalStateException: unexpected docvalues type NONE for field
'listing_lastmodified'
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. That
instance / each shard / any instance ?
>
> Appreciate your help Alex.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-5-0-migration-IllegalStateException-unexpected-docvalues-type-NONE-on-fields-using-docvalues-tp4192477p4192732.html
> Sent from the Solr - User mailing list archive at Nabble.com.
help Alex.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-5-0-migration-IllegalStateException-unexpected-docvalues-type-NONE-on-fields-using-docvalues-tp4192477p4192732.html
Sent from the Solr - User mailing list archive at Nabble.com.
sh index
> on a 5.0, it works. Not sure if there's any other way to mitigate it.
>
> I'll appreciate if someone can share their experience on the same.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-5-0-migration-Illegal
On 3/11/2015 4:45 PM, shamik wrote:
> multiValued="false" required="false" omitNorms="true" docValues="true"
> /> 3/11/2015, 2:14:30 PM ERROR SolrDispatchFilter
> null:java.lang.IllegalStateException: unexpected docvalues type NO
r way to mitigate it.
I'll appreciate if someone can share their experience on the same.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-5-0-migration-IllegalStateException-unexpected-docvalues-type-NONE-on-fields-using-docvalues-tp4192477p4192706.html
Sent from the
Hi,
I've a field which is being used for result grouping. Here's the field
definition.
This started once I did a rolling update from 4.7 to 5.0. I started getting
the error on any group by query --> "SolrDispatchFilter null:java.lang.
IllegalStateException: unexpected d
e's a
full stack trace for another field using docvalues.
Field definition :
3/11/2015, 2:14:30 PM ERROR SolrDispatchFilter
null:java.lang.IllegalStateException: unexpected docvalues type NONE for
field 'DocumentType' (expected=SORTED). Use UninvertingReader or
hema with a
newly built 5.0 index, or if it *only* affects you when you upgrade and
use an existing index from 4.7)
: Date: Wed, 11 Mar 2015 11:02:43 -0700
: From: Shamik Bandopadhyay
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Solr 5.0 --> "I
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:
http://l
13 matches
Mail list logo
