[ https://issues.apache.org/jira/browse/SOLR-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018350#comment-17018350 ]
Chris M. Hostetter commented on SOLR-11746: ------------------------------------------- [~houston] - i'm having a little trouble following what exactly the problem is ... whether you're referring to: * a (modified) patch you have in progress that seems to have a bug but you can't figure out where ** posting the patch for discussion would help) *OR* * that independent of any of the changes discussed here, you've found a bug in that that trying to use {{NormsFieldExistsQuery}} doesn't seem to work with PointsFields (in solr) at all because {{FieldInfo.hasNorms()}} on an existing index is returning false when it shouldn't based on the indexOptions set (in solr) when indexing thta field ** in which case perhaps make a Sub-Task and post an isolated "test only" white box patch asserting what {{FieldInfo.hasNorms()}} returns for a a variety of field types? Either way: a patch with a failing test case and some nocommit comments drawing attention to the problematic bits would be helpful for further discussion. > numeric fields need better error handling for prefix/wildcard syntax -- > consider uniform support for "foo:* == foo:[* TO *]" > ---------------------------------------------------------------------------------------------------------------------------- > > Key: SOLR-11746 > URL: https://issues.apache.org/jira/browse/SOLR-11746 > Project: Solr > Issue Type: Bug > Affects Versions: 7.0 > Reporter: Chris M. Hostetter > Assignee: Houston Putman > Priority: Major > Fix For: master (9.0), 8.5 > > Attachments: SOLR-11746.patch, SOLR-11746.patch, SOLR-11746.patch, > SOLR-11746.patch, SOLR-11746.patch, SOLR-11746.patch > > > On the solr-user mailing list, Torsten Krah pointed out that with Trie > numeric fields, query syntax such as {{foo_d:\*}} has been functionality > equivilent to {{foo_d:\[\* TO \*]}} and asked why this was not also supported > for Point based numeric fields. > The fact that this type of syntax works (for {{indexed="true"}} Trie fields) > appears to have been an (untested, undocumented) fluke of Trie fields given > that they use indexed terms for the (encoded) numeric terms and inherit the > default implementation of {{FieldType.getPrefixQuery}} which produces a > prefix query against the {{""}} (empty string) term. > (Note that this syntax has aparently _*never*_ worked for Trie fields with > {{indexed="false" docValues="true"}} ) > In general, we should assess the behavior users attempt a prefix/wildcard > syntax query against numeric fields, as currently the behavior is largely > non-sensical: prefix/wildcard syntax frequently match no docs w/o any sort > of error, and the aformentioned {{numeric_field:*}} behaves inconsistently > between points/trie fields and between indexed/docValued trie fields. -- 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