Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HSEARCH-917 (
https://hibernate.atlassian.net/browse/HSEARCH-917?atlOrigin=eyJpIjoiZGEw...
)
Re: Add match all terms option when matching in the DSL API (
https://hibernate.atlassian.net/browse/HSEARCH-917?atlOrigin=eyJpIjoiZGEw...
)
I guess the use case is already addressed by SimpleQueryString for the most part, but
there are still details that are not...
In particular I know the simple query string can apply an AND between two clauses
(separated by a space), but I'm not sure what happens when a clause is tokenized into
two separate terms (e.g. wi-fi ). It's quite possible that we end up with an OR
between the two terms, and then we're back to the same old problem.
Elasticsearch has quite advanced settings to define how to behave when trying to match
multiple terms (what this ticket is about) or multiple fields ( HSEARCH-3327 (
https://hibernate.atlassian.net/browse/HSEARCH-3327 ) Open ), and I think it would be
worth having a look.
There are also minor differences between the match predicate and the simple query string
predicate that could make the match predicate preferable in some cases: no support for DSL
converters, no fuzzy option that can be set by the developer, ... All very minor, but they
exist.
Anyway, this is definitely low-priority, at least for Search 6.0.0.Final. I might end up
postponing to 6.1 if we don't have enough time.
(
https://hibernate.atlassian.net/browse/HSEARCH-917#add-comment?atlOrigin=...
) Add Comment (
https://hibernate.atlassian.net/browse/HSEARCH-917#add-comment?atlOrigin=...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100131- sha1:a811519 )