October 2022 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-4620) Simplify the configuration of indexing plan synchronization with the Standalone POJO Mapper

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4149) Support more missing() sort options

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4542) .within() and .withinAny() for the range predicate

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4620) Simplify the configuration of indexing plan synchronization with the Standalone POJO Mapper

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4620) Simplify the configuration of indexing plan synchronization with the Standalone POJO Mapper

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiYzIzOWM3... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4620?atlOrigin=eyJpIjoiYzI... ) HSEARCH-4620 ( https://hibernate.atlassian.net/browse/HSEARCH-4620?atlOrigin=eyJpIjoiYzI... ) Simplify the configuration of indexing plan synchronization with the Standalone POJO Mapper ( https://hibernate.atlassian.net/browse/HSEARCH-4620?atlOrigin=eyJpIjoiYzI... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The ORM mapper has the concept of “automatic indexing synchronization strategy” to easily define what Hibernate Search needs to wait for in order to consider indexing “complete”. The Standalone POJO Mapper only has more low-level features to set the document commit strategy / refresh strategy when building the session. Let’s bring the concept of “automatic indexing synchronization strategy” to the Standalone POJO Mapper. Note that “Automatic Indexing” is not really the right name, as explained in [https://hibernate.atlassian.net/browse/HSEARCH-4616|https://hibernate.atl...] , so we might want to wait until will likely rename it has been renamed before porting the concept to the Standalone POJO mapper later. No big deal though, we can just start with this name for now. ( https://hibernate.atlassian.net/browse/HSEARCH-4620#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4620#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100209- sha1:392b984 )

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4149) Support more missing() sort options

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4542) .within() and .withinAny() for the range predicate

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4679) Automatically simplify and/or predicates with a single clause

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-4679 ( https://hibernate.atlassian.net/browse/HSEARCH-4679?atlOrigin=eyJpIjoiOWR... ) Re: Automatically simplify and/or predicates with a single clause ( https://hibernate.atlassian.net/browse/HSEARCH-4679?atlOrigin=eyJpIjoiOWR... ) I believe the best place to do the simplifying would be inside the boolean builders, e.g.: * org.hibernate.search.backend.elasticsearch.search.predicate.impl.ElasticsearchBooleanPredicate.Builder#build * org.hibernate.search.backend.lucene.search.predicate.impl.LuceneBooleanPredicate.Builder#build We could e.g. introduce something like: if ( ( <only one must clause and no other clause> || <only one should clause and no other clause> ) && <no other option set>) { <just return the inner predicate> } One thing that worries me, though, is if we introduce new options in the boolean predicate and forget to test for them in <no other option set> in the condition above. Then we’d end up ignoring these options in some cases. I wonder if there’s some way to prevent that from ever happening, just by implementing the build in some smart way… ( https://hibernate.atlassian.net/browse/HSEARCH-4679#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4679#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=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100209- sha1:392b984 )

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4679) Automatically simplify and/or predicates with a single clause

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4615) Move more configuration of the Standalone POJO mapper to configuration properties

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues October 2022