Waldemar Kłaczyński (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HSEARCH-3325 (
https://hibernate.atlassian.net/browse/HSEARCH-3325?atlOrigin=eyJpIjoiMjk...
)
Re: Search 6 groundwork - Restore support for full-text filters (
https://hibernate.atlassian.net/browse/HSEARCH-3325?atlOrigin=eyJpIjoiMjk...
)
Of course, also from previous versions, the definition of native filters was just an
addition, the same could always be obtained by the query itself. In the previous version,
you could also make an external library containing static methods that return ready-made
filters. However, assigning a filter to an object type greatly simplifies management,
especially at work where many people do programming. For large projects, this is very
useful for improving the readability of the code.
Previously, there was a similar solution in version 5.4.
public static class TestFilter {
public static Query filter( String match) {
return IntPoint.newExactQuery( "fieldName" , match );
}
}
FullTextQuery fullTextQuery = fullTextEntityManager
.createFullTextQuery( new BooleanQuery.Builder()
.add(TestFilter.filter( "blablabla" ),
BooleanClause.Occur.FILTER),
Assortment.class);
But such filters made it easier to organize the code. I think it's easy to reproduce
in version 6.x. I will try to give a ready solution.
(
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:ecfcbe7 )