You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Chris M. Hostetter (Jira)" <ji...@apache.org> on 2020/09/14 21:23:00 UTC
[jira] [Updated] (SOLR-14859) [* TO *] queries on DateRange fields
miss results
[ https://issues.apache.org/jira/browse/SOLR-14859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris M. Hostetter updated SOLR-14859:
--------------------------------------
Attachment: SOLR-14859.patch
Status: Open (was: Open)
Attaching a test patch demonstrating the failure, as well as a nocommit schema change validating the the "work around" i suggested in my last comment seems to work.
(DateRangeFieldTest actually already had a {{\[* TO *\]}} test -- but it was using the "field" qparser and didn't fail ... i guess because that parser bypasses the special "exists" logic added to FieldType in SOLR-11746 and was using the DateRangeField's special range syntax? not certain)
----
bq. Long term it seems like DateRangeField should use ... and "fail" if a user tries to override them when schema options – since they are immutable
"fail" is probably too strong ... we can probably just WARN if users try to set a field/fieldType property that we know is (and has always been) ignored.
> [* 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
> Priority: Major
> Attachments: 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: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org