[ 
https://issues.apache.org/jira/browse/SOLR-14859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197966#comment-17197966
 ] 

Jason Gerlowski edited comment on SOLR-14859 at 9/17/20, 9:16 PM:
------------------------------------------------------------------

Thanks for the quick review Hoss - I made the changes you suggested and it 
looks good with manual tests.  Working on tests now - it looks like it broke 
something in DateRangeFieldTest so still tracking that down...

bq. Or we could change the api of checkSchemaField so that can return the 
'final' properties the SchemaField should use

I thought about this a bit too - {{checkSchemaField}} returns void but could 
return a new SchemaField that the FieldType creates based on whatever changes 
it wants to make.  But agreed that anything like that is overkill for what we 
want here. 


was (Author: gerlowskija):
Thanks for the quick review Hoss - I made the changes you suggested and it 
looks good with manual tests.  Working on tests now - it looks like it broke 
something in DateRangeFieldTest so still tracking that down...

> [* 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to