[
https://issues.apache.org/jira/browse/SOLR-9187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471202#comment-15471202
]
Colvin Cowie commented on SOLR-9187:
------------------------------------
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.
{noformat}
<field name="f_EVE64" type="boolean" indexed="true" stored="true"
required="false" multiValued="false"/>
<fieldType name="boolean" class="solr.BoolField" sortMissingLast="true"/>
{noformat}
{noformat}
"response":{"numFound":2,"start":0,"maxScore":1.0,"docs":[
{
"id":"124",
"f_EVE64":false,
"_version_":1544828487600177152},
{
"id":"123",
"f_EVE64":false,
"_version_":1544828492458229760}]
},
"facet_counts":{
"facet_queries":{},
"facet_fields":{
"f_EVE64":[
"false",1,
"true",1]},
{noformat}
Could toExternal() perhaps fallback to how it originally behaved? e.g.
{noformat}
if (f.binaryValue() == null) {
return indexedToReadable(f.stringValue());
}
{noformat}
> Support dates and booleans in /export handler, support boolean DocValues
> fields
> -------------------------------------------------------------------------------
>
> Key: SOLR-9187
> URL: https://issues.apache.org/jira/browse/SOLR-9187
> Project: Solr
> Issue Type: Improvement
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Fix For: 6.2, master (7.0)
>
> Attachments: SOLR-9187.patch, SOLR-9187.patch, SOLR-9187.patch
>
>
> Since these can be DV fields it seems like it should. The first-level problem
> is that SortingResponseWriter doesn't check for date types as a legal export
> value. Whether there are repercussions elsewhere I don't know yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
