You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Prashant Saraswat <pr...@pixalsoft.com> on 2017/04/13 02:04:50 UTC

unexpected docvalues type NONE

Hi,

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:

<field name="transaction_amount_display" type="tdouble" indexed="true"
stored="true" required="false"/>

I suddenly start getting this error for certain queries ( not all queries
and even for queries that have nothing to do 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' (expected one of [BINARY, NUMERIC, SORTED,
SORTED_NUMERIC, SORTED_SET]). Re-index with correct docvalues type.
        at org.apache.lucene.index.DocValues.checkField(DocValues.java:212)
        at
org.apache.lucene.index.DocValues.getDocsWithField(DocValues.java:324)
        at
org.apache.solr.search.SolrIndexSearcher.decorateDocValueFields(SolrIndexSearcher.java:783)
        at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:136)
        at org.apache.solr.response.DocsStreamer.next(DocsStreamer.java:52)
        at
org.apache.solr.response.BinaryResponseWriter$Resolver.writeResultsBody(BinaryResponseWriter.java:124)
        at
org.apache.solr.response.BinaryResponseWriter$Resolver.writeResults(BinaryResponseWriter.java:143)
        at
org.apache.solr.response.BinaryResponseWriter$Resolver.resolve(BinaryResponseWriter.java:87)
        at
org.apache.solr.common.util.JavaBinCodec.writeVal(JavaBinCodec.java:234)

-- 
<http://www.linkedin.com/pub/prashant-saraswat/0/909/b07/>

Re: unexpected docvalues type NONE

Posted by Prashant Saraswat <pr...@pixalsoft.com>.
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 <ap...@elyograg.org> wrote:

> 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:
> >
> > <field name="transaction_amount_display" type="tdouble" indexed="true"
> > stored="true" required="false"/>
> >
> > I suddenly start getting this error for certain queries ( not all
> queries and even for queries that have nothing to do 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?
>
> The error suggests that the definition for listing_lastmodified was
> altered at some point without reindexing.  I'm guessing that the field
> did NOT have docValues originally, then docValues was enabled.
>
> When the docValues setting for a field is changed, deleting the index
> and rebuilding it is required.  In 6.4.0, simple field types like the
> TrieDoubleField used for tdouble have docValues enabled by default.
>
> Adding a field should never require a reindex, unless you want to
> populate that field in documents that have already been indexed.
>
> Thanks,
> Shawn
>
>


-- 
<http://www.linkedin.com/pub/prashant-saraswat/0/909/b07/>

Re: unexpected docvalues type NONE

Posted by Shawn Heisey <ap...@elyograg.org>.
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:
>
> <field name="transaction_amount_display" type="tdouble" indexed="true"
> stored="true" required="false"/>
>
> I suddenly start getting this error for certain queries ( not all queries and even for queries that have nothing to do 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?

The error suggests that the definition for listing_lastmodified was
altered at some point without reindexing.  I'm guessing that the field
did NOT have docValues originally, then docValues was enabled.

When the docValues setting for a field is changed, deleting the index
and rebuilding it is required.  In 6.4.0, simple field types like the
TrieDoubleField used for tdouble have docValues enabled by default.

Adding a field should never require a reindex, unless you want to
populate that field in documents that have already been indexed.

Thanks,
Shawn