July 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-4755) Upgrade to Spring Boot 3 for -orm6 artifacts

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4755) Upgrade to Spring Boot 3 for -orm6 artifacts

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-4555) Upgrade to JBoss logging 3.5.2.Final

by Yoann Rodière (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HSEARCH-3327) Add options for match predicates targeting multiple fields

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=eyJpIjoiM2ZhODky... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-3327?atlOrigin=eyJpIjoiM2Z... ) HSEARCH-3327 ( https://hibernate.atlassian.net/browse/HSEARCH-3327?atlOrigin=eyJpIjoiM2Z... ) Add options for match predicates targeting multiple fields ( https://hibernate.atlassian.net/browse/HSEARCH-3327?atlOrigin=eyJpIjoiM2Z... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *Note*: This is slightly different from [ HSEARCH-917 ] and [https://hibernate.atlassian.net/browse/ HSEARCH-2589 |https://hibernate.atlassian.net/browse/HSEARCH-2589|smart-link] , though related. This ticket is about the behavior when a single predicate target multiple fields, while the others are about the behavior when a single predicate has multiple search terms. We should offer additional parameters to match predicates allowing to select exactly how we want the predicate to behave when multiple fields are targeted: * how documents are matched: at least one match is required per field, or at least one on any field, ... * how score is computed. We will probably have to move the handling of multiple fields to the backend layer, i.e. not create a boolean junction in the engine and ask the backend to create one predicate for each field, but instead just ask the backend to create a single predicate for *all* the fields. See for example the “multi-match” query in Elasticsearch: [ https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl... |https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-multi-match-query.html] And in particular the "type" parameter: [ https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl... |https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-multi-match-query.html#multi-match-types] ( https://hibernate.atlassian.net/browse/HSEARCH-3327#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3327#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#100228- sha1:e911e2c )

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16853) Setting Named Query Parameters Is VERY Slow

by Andrea Boriero (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16853) Setting Named Query Parameters Is VERY Slow

by Andrea Boriero (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16865) Multiselect CriteriaQuery fails with "Could not locate TableGroup"

by Marco Belladelli (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16865) Multiselect CriteriaQuery fails with "Could not locate TableGroup"

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16865 ( https://hibernate.atlassian.net/browse/HHH-16865?atlOrigin=eyJpIjoiYWM4OW... ) Re: Multiselect CriteriaQuery fails with "Could not locate TableGroup" ( https://hibernate.atlassian.net/browse/HHH-16865?atlOrigin=eyJpIjoiYWM4OW... ) The way you’re constructing this multiselect Criteria Query is wrong - you are creating a query to get the Root , than creating another query and re-using that root object there without specifying a from. I'm afraid this used to work in Hibernate 5 by chance, but even JPA's AbstractQuery#getRoots() javadoc ( https://jakarta.ee/specifications/persistence/3.1/apidocs/jakarta.persist... ) says: > > > > … Modifications to the set do not affect the query. > > The correct way to do this in your reproducer would be something like this: CriteriaQuery<TestDto> queryMulti = criteriaBuilder.createQuery(TestDto.class); Root<TestTbl> root = queryMulti.from(TestTbl.class); CriteriaQuery<?> multiselect = queryMulti.multiselect(root.get(TestTbl_.id)); Closing this issue as the behavior in Hibernate 6 is consistent with the spec. If you have any additional doubt or request feel free to leave a comment. ( https://hibernate.atlassian.net/browse/HHH-16865#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16865#add-comment?atlOrigin=ey... ) 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#100228- sha1:e911e2c )

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-15547) Multi-fetch with a single bag returns duplicates

by Andrea Boriero (JIRA)

2 years, 2 months

1
0
0 / 0

[JIRA] (HHH-16810) Fail to delete entity with a composite id using an @IdClass with one of its fields mapped from the id of a @ManyToOne association

by Andrea Boriero (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 July 2023