June 2023 - hibernate-issues - Jboss List Archives

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMTUyOTg4... ) / Remove Feature ( https://hibernate.atlassian.net/browse/HSEARCH-4868?atlOrigin=eyJpIjoiMTU... ) HSEARCH-4868 ( https://hibernate.atlassian.net/browse/HSEARCH-4868?atlOrigin=eyJpIjoiMTU... ) Drop compatibility with Elasticsearch 5.x/6.x ( https://hibernate.atlassian.net/browse/HSEARCH-4868?atlOrigin=eyJpIjoiMTU... ) Issue Type: Remove Feature Assignee: Unassigned Components: backend-elasticsearch Created: 08/Jun/2023 01:50 AM Fix Versions: 7.0-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Because: * Elastic stopped supporting Elasticsearch 6.x more than a year ago, on Feb 10, 2022 ( source ( https://endoflife.date/elasticsearch ) ) * It’s been so long since Elasticsearch 5.x stopped being supported that I can’t even find the date * People wanting to stick to older Elasticsearch versions can stick to older Hibernate Search versions (Hibernate Search 6.2) * Testing many versions of Elasticsearch has a cost: both financially (AWS EC2 costs) and operationally (builds take much longer) We’ll need to: * Adapt the dialect factory and tests * Remove now-unnecessary dialects and the resulting dead code, e.g. Elasticsearch56WorkFactory or org.hibernate.search.backend.elasticsearch.work.impl.SearchWork.Builder#forElasticsearch62AndBelow * Remove now-unnecessary testing conditions (e.g. org.hibernate.search.util.impl.integrationtest.backend.elasticsearch.dialect.ElasticsearchTestDialect#isEmptyMappingPossible or org.hibernate.search.integrationtest.backend.elasticsearch.testsupport.util.ElasticsearchTckBackendFeatures#geoPointIndexNullAs ) * Remove mentions of older versions in the documentation * Remove Elasticsearch 5.x/6.x environments from our Jenkinsfiles ( https://hibernate.atlassian.net/browse/HSEARCH-4868#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4868#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#100226- sha1:b8bf2ee )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16587) WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field :

by Guillaume (JIRA)

Guillaume ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=712020%... ) *commented* on HHH-16587 ( https://hibernate.atlassian.net/browse/HHH-16587?atlOrigin=eyJpIjoiOTkzOD... ) Re: WARN [org.hib.met.int.MetadataContext] (JPA Startup Thread) HHH015011: Unable to locate static metamodel field : ( https://hibernate.atlassian.net/browse/HHH-16587?atlOrigin=eyJpIjoiOTkzOD... ) We have the same with SB3.0.7 and HB6.1.7, even with @JdbcTypeCode(SqlTypes.JSON) instead of hypersistence ( https://hibernate.atlassian.net/browse/HHH-16587#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16587#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#100226- sha1:b8bf2ee )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16770) Entity valued path expansion for GROUP BY clause causes problems for in-subquery predicates

by Marco Belladelli (JIRA)

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16409) SQLGrammarException when selecting property of grouped join association

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16409 ( https://hibernate.atlassian.net/browse/HHH-16409?atlOrigin=eyJpIjoiZTk1Mz... ) Re: SQLGrammarException when selecting property of grouped join association ( https://hibernate.atlassian.net/browse/HHH-16409?atlOrigin=eyJpIjoiZTk1Mz... ) George Gastaldi ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I’ve created https://hibernate.atlassian.net/browse/HHH-16770 for this issue. Note that the problem doesn’t seem to be related to a JSON type field used in the GROUP BY clause, rather we should not expand the group by clause in a subquery predicate since the selection itself is not expanded. ( https://hibernate.atlassian.net/browse/HHH-16409#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16409#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#100226- sha1:b8bf2ee )

2 years, 10 months

1
0
0 / 0

[JIRA] (HHH-16770) Entity valued path expansion for GROUP BY clause causes problems for in-subquery predicates

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZmI0ZGVmNjgz... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16770?atlOrigin=eyJpIjoiZmI0ZG... ) HHH-16770 ( https://hibernate.atlassian.net/browse/HHH-16770?atlOrigin=eyJpIjoiZmI0ZG... ) Entity valued path expansion for GROUP BY clause causes problems for in-subquery predicates ( https://hibernate.atlassian.net/browse/HHH-16770?atlOrigin=eyJpIjoiZmI0ZG... ) Issue Type: Bug Assignee: Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) Created: 08/Jun/2023 01:18 AM Priority: Major Reporter: Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) This change https://hibernate.atlassian.net/browse/HHH-16409 introduced entity valued path expansion for GROUP BY clauses when they were selected. This is causing problems when the same logic is used for an in-clause subquery predicate. This is an example HQL that triggers the problem: select pr from PlatformRelease pr where pr.unlisted = false and pr.platformStream.platform.platformType = ' C ' and (pr.platformStream, pr.versionSortable) in ( select pr2.platformStream, max (pr2.versionSortable) from PlatformRelease pr2 where pr2.platformStream.unlisted = false and pr2.unlisted = false group by pr2.platformStream ) order by pr.versionSortable desc , pr.platformStream.platform.isDefault desc The error was originally reported in this Quarkus issue: https://github.com/quarkusio/quarkus/issues/33895. ( https://hibernate.atlassian.net/browse/HHH-16770#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16770#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#100226- sha1:b8bf2ee )

2 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-4866) Deprecate hibernate.search.automatic_indexing.enable_dirty_checks for removal

by Automation for Jira (JIRA)

2 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2023