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

David Smiley commented on SOLR-14859:
-------------------------------------

Calling {{args.putAll(FIELD_TYPE_INVARIANTS);}} in {{setArgs}} has the effect 
of making Solr think the user set all those invariant args when he/she didn't 
actually.  A consequence of this is that Solr's schema APIs will return all 
these invariants, which happens for example when writing a managed schema.  
That later triggers warnings about setting properties you aren't supposed to.  
See the linked issue SOLR-15333

> [* TO *] queries on DateRange fields miss results
> -------------------------------------------------
>
>                 Key: SOLR-14859
>                 URL: https://issues.apache.org/jira/browse/SOLR-14859
>             Project: Solr
>          Issue Type: Improvement
>          Components: query parsers
>    Affects Versions: 8.5
>            Reporter: Jason Gerlowski
>            Assignee: Jason Gerlowski
>            Priority: Major
>             Fix For: 8.6.3, 8.7, main (9.0)
>
>         Attachments: SOLR-14859.patch, 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.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to