[
https://issues.apache.org/jira/browse/SOLR-14859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197996#comment-17197996
]
Chris M. Hostetter commented on SOLR-14859:
-------------------------------------------
bq. Working on tests now
Check out BadIndexSchemaTest for examples of testing that we "fail" expectedly
on fields/types with bad options
bq. ... checkSchemaField returns void but could return a new SchemaField that
the FieldType creates based on whatever changes it wants to make.
Except that in the current lifecycle, FT.checkSchemaField is called from the
SchemaField constructor -- so like i said: we'd either have to seriously change
the lifecycle/API of SchemaField, or make the constructor override it's own
props by the output of checkSchemaField ... but i think we're in agreement we
don't wnat to go down the road : )
> [* 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,
> 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]