[
https://issues.apache.org/jira/browse/SOLR-15463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361093#comment-17361093
]
Timothy Potter commented on SOLR-15463:
---------------------------------------
hmmm ... I don't know if we should allow % unless the user is using LIKE? fwiw
~ {{WHERE a_s='hello*'}} isn't really a proper SQL expression but I think we
should support it with * since it is Solr specific but seems like if users want
to use %, they should use the LIKE operator instead, i.e. Solr needs to
support: {{WHERE a_s LIKE 'hello%'}} and {{WHERE a_s='hello*'}} (where the
latter is supported for legacy purposes, even though it never probably worked)
> 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]
