You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Tomas Eduardo Fernandez Lobbe (Jira)" <ji...@apache.org> on 2020/01/09 18:58:00 UTC
[jira] [Comment Edited] (SOLR-11746) numeric fields need better
error handling for prefix/wildcard syntax -- consider uniform support for
"foo:* == foo:[* TO *]"
[ https://issues.apache.org/jira/browse/SOLR-11746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012151#comment-17012151 ]
Tomas Eduardo Fernandez Lobbe edited comment on SOLR-11746 at 1/9/20 6:57 PM:
------------------------------------------------------------------------------
bq. I agree with Hoss's boxed new opinion
+1
bq. {{price:* - Valid, Matches no docs}}
I think this should be considered a bug, thus, we wouldn't need back compat here, right?
If we consider the case of {{numeric:*}} not turning into an "exists" query for float/doubles then there shouldn't be any compatibility issues, or am I missing something?
was (Author: tomasflobbe):
bq. I agree with Hoss's boxed new opinion
+1
bq. `price:* - Valid, Matches no docs`
I think this should be considered a bug, thus, we wouldn't need back compat here, right?
If we consider the case of `numeric:*` not turning into an "exists" query for float/doubles then there shouldn't be any compatibility issues, or am I missing something?
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org