[
https://issues.apache.org/jira/browse/SOLR-15463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361246#comment-17361246
]
Aroop commented on SOLR-15463:
------------------------------
yes makes sense only for LIKE. In my opinion the `=` operator maps to an
exact-match operation from the user's mental model.
I do understand there are some backward compatibility concerns to keep this for
equals.
> Solr SQL predicate with wildcard doesn't match, needs the complex phrase
> query parser
> -------------------------------------------------------------------------------------
>
> Key: SOLR-15463
> URL: https://issues.apache.org/jira/browse/SOLR-15463
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Parallel SQL
> Reporter: Timothy Potter
> Assignee: Timothy Potter
> Priority: Major
> Labels: RobustSQL
>
> I have a query:
> {code}
> SELECT a_s, count(*) as cnt FROM $ALIAS WHERE a_s='hello*' GROUP BY a_s ORDER
> BY count(*) desc LIMIT 10
> {code}
> This fails to match documents that should match. The problem is the query
> that gets generated is {{q=a_s:"hello*"}}.
> Query should get generated like:
> {code}
> {!complexphrase}a_s:"hello*"
> {code}
> which matches ...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
