[
https://issues.apache.org/jira/browse/SOLR-14859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198540#comment-17198540
]
Chris M. Hostetter commented on SOLR-14859:
-------------------------------------------
latest patch looks good to me ... a few nit-picks...
* why did the Logger change from private to protected?
** (i thought check/precommit complained about non-private loggers?)
* i would suggest adding a few javadoc {{@see}} pointers:
** FIELD_TYPE_INVARIANTS -> PrefixTreeStrategy#FIELD_TYPE
** checkSchemaField -> #FIELD_TYPE_INVARIANTS
*** (since it's not used directly in this method, but the logic is realted so
people reading it should be aware of it and read it's docs)
> [* TO *] queries on DateRange fields miss results
> -------------------------------------------------
>
> Key: SOLR-14859
> URL: https://issues.apache.org/jira/browse/SOLR-14859
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: query parsers
> Affects Versions: 8.5
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Major
> Attachments: SOLR-14859.patch, SOLR-14859.patch, SOLR-14859.patch,
> SOLR-14859.patch, SOLR-14859.patch, query-debug.png, reproduce.sh, schema.png
>
>
> "exists" queries ({{[* TO *]}}) on DateRange fields return 0 results
> regardless of docs in the index with values in that field.
> The issue appears to be that the query is converted into a
> {{NormsFieldExistsQuery}}, even though DateRangeField uses omitNorms=true by
> default. Probably introduced by SOLR-11746's changes to these optimizable
> range queries.
> I've attached a script to reproduce the issue (tested on Solr 8.6.2) and
> screenshots showing showing schema and query-parsing info for the
> reproduction.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]