Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HSEARCH-3325 (
https://hibernate.atlassian.net/browse/HSEARCH-3325?atlOrigin=eyJpIjoiM2I...
)
Re: Search 6 groundwork - Restore support for full-text filters (
https://hibernate.atlassian.net/browse/HSEARCH-3325?atlOrigin=eyJpIjoiM2I...
)
We're already working on making nested predicates optional in HSEARCH-3752 (
https://hibernate.atlassian.net/browse/HSEARCH-3752 ) Pull Request Sent , so the part you
added about getting the nested path won't be useful in the next version of Hibernate
Search.
In the light of this, what exactly do full-text filters bring compared to this solution,
which is simpler and type-safe?
public static class TestFilterFactory {
public SearchPredicate filter(SearchPredicateFactory f, String match) {
return f.match().field( fieldPath )
.matching( match )
.toPredicate();
}
}
() -> scope.query()
.where( f -> f.bool()
.minimumShouldMatchNumber( 3 )
.should( TestFilterFactory.filter( "match_fieldName" , "blablabla"
) )
.should( TestFilterFactory.filter( "nested.match_fieldName" ,
"blablabla" ) );
} ).toQuery()
(
https://hibernate.atlassian.net/browse/HSEARCH-3325#add-comment?atlOrigin...
) Add Comment (
https://hibernate.atlassian.net/browse/HSEARCH-3325#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#100121- sha1:a2b3dcc )