lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Created] (SOLR-9490) BoolField always returning false for non-DV fields?
Date Thu, 08 Sep 2016 17:26:22 GMT
Hoss Man created SOLR-9490:

             Summary: BoolField always returning false for non-DV fields?
                 Key: SOLR-9490
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
    Affects Versions: 6.2
            Reporter: Hoss Man
            Priority: Critical

2 diff users posted comments in SOLR-9187 indicating that changes introduced in that issue
have broken BoolFields that do *not* use DocValues...

Hi, I've just picked up 6.2.0. It seems that the change to toExternal() in BoolField now means
that booleans without DocValues return null, which then turns into Boolean.FALSE in toObject()
regardless of whether the value is true or false.

e.g. with this schema, facet counts are correct, the returned values are wrong.
<field name="f_EVE64" type="boolean" indexed="true" stored="true" required="false" multiValued="false"/>
<fieldType name="boolean" class="solr.BoolField" sortMissingLast="true"/>
Could toExternal() perhaps fallback to how it originally behaved? e.g.
if (f.binaryValue() == null) {
      return indexedToReadable(f.stringValue());

I downloaded solr version 6.2.0 (6.2.0 764d0f19151dbff6f5fcd9fc4b2682cf934590c5 - mike - 2016-08-20
05:41:37) and installed my core.

In my schema.xml i have an field like following :

<field name="stock_status" type="boolean" indexed="true" stored="true" multiValued="false"/>

Now i am accessing this field using SolrJ (6.1.0). But i am always getting false value for
above field even though it contains true boolean value. This is happening for all boolean

http://localhost:8983/solr...wt=javabin&version=2 HTTP/1.1

It is working fine in other response writer.

If i change the solr version to 6.1.0, with same SolrJ, it starts working. So clearly this
is a bug in version 6.2.0.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message