August 2022 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-4689) Upgrade to HCANN 6.0.4.Final for -orm6 artifacts

by Automation for Jira (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HSEARCH-4689) Upgrade to HCANN 6.0.4.Final for -orm6 artifacts

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HSEARCH-4670) Fix flaky test org.hibernate.search.integrationtest.mapper.orm.massindexing.MassIndexingErrorCustomBackgroundFailureHandlerIT(default-default-database-oracle)

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15072) Default EmbeddableInstantiator for records

by Christian Beikov (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15470) Prevent N+1 problem on successful join results

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *closed* an issue as *Won't Do* Hibernate does that because it works with equals/hashCode when it comes to strings(varchar), which is always case sensitive. So the result of the query contains entities with identifiers `aaa`, `bbb` etc. and the foreign key value, by which Hibernate then tries to load objects for the associations, have the values `AAA`, `BBB` etc. For these values Hibernate can not find entities in the persistence context, so it will consult the database again. Unless you configured a case insensitive collation, the subsequent selects will produce no results. Overall, there is nothing Hibernate can do here. You will just have to fix your data. Also see the discussion with a user on Discourse that had a similar issue: https://discourse.hibernate.org/t/how-can-i-make-a-resultsetmapping-for-a... ( https://discourse.hibernate.org/t/how-can-i-make-a-resultsetmapping-for-a... ) Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjM0NTQ3ZTBi... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15470?atlOrigin=eyJpIjoiYjM0NT... ) HHH-15470 ( https://hibernate.atlassian.net/browse/HHH-15470?atlOrigin=eyJpIjoiYjM0NT... ) Prevent N+1 problem on successful join results ( https://hibernate.atlassian.net/browse/HHH-15470?atlOrigin=eyJpIjoiYjM0NT... ) Change By: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Assignee: Unassigned Christian Beikov Resolution: Won't Do Status: Open Closed ( https://hibernate.atlassian.net/browse/HHH-15470#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15470#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#100206- sha1:1e36365 )

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15470) Prevent N+1 problem on successful join results

by Jin Kwon (JIRA)

Jin Kwon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjdmNjU5Yzhi... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15470?atlOrigin=eyJpIjoiYjdmNj... ) HHH-15470 ( https://hibernate.atlassian.net/browse/HHH-15470?atlOrigin=eyJpIjoiYjdmNj... ) Prevent N+1 problem on successful join results ( https://hibernate.atlassian.net/browse/HHH-15470?atlOrigin=eyJpIjoiYjdmNj... ) Change By: Jin Kwon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When I tried to join two tables with a VARCHAR column with different case(upper/lower), Hibernate still does N+1 select even joined entries found. I have two tables with no FK. Table A’s column contains lowercased values while table B’s column contains uppercased values. Note that there is no FK, and the join process succeeds. Hibernate does this, first. {{SELECT b.*, a.* FROM b outer join a ON b.col = a.col;}} which selects all tuples like charm. {{b.col a.col ...}} {{ AAA aaa ...}} {{ BBB bbb. ...}} And it also executes queries for all (already) joined tuples. (N+1) {{SELECT * FROM a WHERE a.col = 'AAA';}} {{SELECT * FROM a WHERE a.col = 'BBB';}} {{SELECT * FROM a WHERE a.col = 'CCC';}} I have a workaround using {{@JoinFomula}}. {code:java} @Valid @NotFound(action = NotFoundAction.IGNORE) // -> EAGER! // partner_id 컬럼의 값들이 uppercase 다. // join 은 되는데... hibernate 가 (잘 찾고도) N+1 문제를 일으킨다. @JoinFormula("LOWER(" + COLUMN_NAME_PARTNER_ID + ")") // @@? @MapsId(MappedPartnerSearchRestriction_.PARTNER_ID) @ManyToOne(optional = /*false*/true, fetch = FetchType.LAZY) //@JoinColumn(name = COLUMN_NAME_PARTNER_ID, nullable = false, insertable = false, updatable = false, // foreignKey = @ForeignKey(ConstraintMode.NO_CONSTRAINT)) @EqualsAndHashCode.Exclude @ToString.Exclude private Some some;{code} But the solution relies on speculations (b.col is always uppercased and a.col is always lowercased) Do we have any chance for enhancement? ( https://hibernate.atlassian.net/browse/HHH-15470#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15470#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#100206- sha1:1e36365 )

1 year, 8 months

1
0
0 / 0

[JIRA] (HHH-15470) Prevent N+1 problem on successful join results

by Jin Kwon (JIRA)

Jin Kwon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjYzNjI0YzM1... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15470?atlOrigin=eyJpIjoiZjYzNj... ) HHH-15470 ( https://hibernate.atlassian.net/browse/HHH-15470?atlOrigin=eyJpIjoiZjYzNj... ) Prevent N+1 problem on successful join results ( https://hibernate.atlassian.net/browse/HHH-15470?atlOrigin=eyJpIjoiZjYzNj... ) Issue Type: Improvement Affects Versions: 5.6.10 Assignee: Unassigned Components: hibernate-entitymanager Created: 30/Aug/2022 00:14 AM Environment: Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63) Maven home: /opt/homebrew/Cellar/maven/3.8.6/libexec Java version: 18.0.2.1, vendor: Eclipse Adoptium, runtime: /Library/Java/JavaVirtualMachines/temurin-18.jdk/Contents/Home Default locale: en_KR, platform encoding: UTF-8 OS name: "mac os x", version: "12.5", arch: "aarch64", family: "mac" Labels: n+1 Priority: Minor Reporter: Jin Kwon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When I tried to join two tables with a VARCHAR column with different case(upper/lower), Hibernate still does N+1 select even joined entries found. I have two tables with no FK. Table A’s column contains lowercased values while table B’s column contains uppercased values. Note that there is no FK, and the join process succeeds. Hibernate does this, first. SELECT b. *, a.* FROM b outer join a ON b.col = a.col; which selects all tuples like charm. b.col a.col ... {{ AAA aaa ...}} {{ BBB bbb. ...}} And it also executes queries for all (already) joined tuples. (N+1) SELECT * FROM a WHERE a.col = 'AAA'; SELECT * FROM a WHERE a.col = 'BBB'; SELECT * FROM a WHERE a.col = 'CCC'; I have a workaround. @Valid @NotFound(action = NotFoundAction.IGNORE) // -> EAGER! // partner_id 컬럼의 값들이 uppercase 다. // join 은 되는데... hibernate 가 (잘 찾고도) N+1 문제를 일으킨다. @JoinFormula( "LOWER(" + COLUMN_NAME_PARTNER_ID + ")" ) // @@? @MapsId(MappedPartnerSearchRestriction_.PARTNER_ID) @ManyToOne(optional = /* false */ true , fetch = FetchType.LAZY) //@JoinColumn(name = COLUMN_NAME_PARTNER_ID, nullable = false , insertable = false , updatable = false , // foreignKey = @ForeignKey(ConstraintMode.NO_CONSTRAINT)) @EqualsAndHashCode.Exclude @ToString.Exclude private Some some; But the solution relies on speculations (b.col is always uppercased and a.col is always lowercased) Do we have any chance for enhancement? ( https://hibernate.atlassian.net/browse/HHH-15470#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15470#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#100206- sha1:1e36365 )

1 year, 8 months

1
0
0 / 0

[JIRA] (HSEARCH-4687) Fix flaky test org.hibernate.search.integrationtest.mapper.orm.coordination.outboxpolling.automaticindexing.OutboxPollingAutomaticIndexingDynamicShardingRebalancingIT(coord-outbox-default-database-cockroachdb)

by Automation for Jira (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HSEARCH-4689) Upgrade to HCANN 6.0.4.Final for -orm6 artifacts

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

[JIRA] (HSEARCH-4689) Upgrade to HCANN 6.0.4.Final for -orm6 artifacts

by Yoann Rodière (JIRA)

1 year, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2022