January 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16043) Hibernate 6.x breaks collection batch fetching

by Christian Beikov (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16097) Move all tests from documentation into hibernate-core

by Andrea Boriero (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16097) Move all tests from documentation into hibernate-core

by Andrea Boriero (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16099) Excessive warnings being logged about "entity was modified, but it won't be updated because the property is immutable"

by Steve Ebersole (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16099) Excessive warnings being logged about "entity was modified, but it won't be updated because the property is immutable"

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjg2Y2U0NGY4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16099?atlOrigin=eyJpIjoiMjg2Y2... ) HHH-16099 ( https://hibernate.atlassian.net/browse/HHH-16099?atlOrigin=eyJpIjoiMjg2Y2... ) Excessive warnings being logged about "entity was modified, but it won't be updated because the property is immutable" ( https://hibernate.atlassian.net/browse/HHH-16099?atlOrigin=eyJpIjoiMjg2Y2... ) Issue Type: Bug Assignee: Unassigned Created: 25/Jan/2023 06:53 AM Fix Versions: 6.2.0 Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) It seems we’re very frequently logging the message “ The [%s] property of the [%s] entity was modified, but it won't be updated because the property is immutable. " at WARN level, even while it seems there is no reason for it. Benchmark results are being negatively affected, and we’re logging this very frequently under load. ( https://hibernate.atlassian.net/browse/HHH-16099#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16099#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#100214- sha1:3d33cb1 )

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16098) Rework BatchFetchQueue to allow registering eager batch keys

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZTVhMTdkMmQ0... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-16098?atlOrigin=eyJpIjoiZTVhMT... ) HHH-16098 ( https://hibernate.atlassian.net/browse/HHH-16098?atlOrigin=eyJpIjoiZTVhMT... ) Rework BatchFetchQueue to allow registering eager batch keys ( https://hibernate.atlassian.net/browse/HHH-16098?atlOrigin=eyJpIjoiZTVhMT... ) Issue Type: Improvement Assignee: Unassigned Components: hibernate-core Created: 25/Jan/2023 06:30 AM Fix Versions: 6.wishlist Priority: Major Reporter: Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) BatchFetchQueue#batchLoadableEntityKeys unnecessarily holds entity key objects, when only the identifier is needed. Also, it’s a bit of a bummer that initializers have to maintain a separate set of entity keys which they use to then eagerly load data when reaching Initializer#endLoading. I would suggest we rework BatchFetchQueue#batchLoadableEntityKeys to rather hold a new object, which contains a flag eager and at the end of processing, we iterate through BatchFetchQueue#batchLoadableEntityKeys and initialize the ones with eager flags set. ( https://hibernate.atlassian.net/browse/HHH-16098#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16098#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#100214- sha1:3d33cb1 )

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16091) AbstractStandardBasicType to avoid megamorphic dispatch when dealing with AbstractClassJavaType

by Sanne Grinovero (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16005) @BatchSize with @ManyToMany does not work as expected when migrating 5 -> 6

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16005 ( https://hibernate.atlassian.net/browse/HHH-16005?atlOrigin=eyJpIjoiZjQ2Zj... ) Re: @BatchSize with @ManyToMany does not work as expected when migrating 5 -> 6 ( https://hibernate.atlassian.net/browse/HHH-16005?atlOrigin=eyJpIjoiZjQ2Zj... ) Hello, I did some tests and the solution for https://hibernate.atlassian.net/browse/HHH-16043 ( https://hibernate.atlassian.net/browse/HHH-16043 ) should solve your problem too: the query to retrieve the tags was executed just once with the 5 Article IDs - thanks to batching - and no more queries were triggered. ( https://hibernate.atlassian.net/browse/HHH-16005#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16005#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#100214- sha1:3d33cb1 )

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16005) @BatchSize with @ManyToMany does not work as expected when migrating 5 -> 6

by Marco Belladelli (JIRA)

1 year, 7 months

1
0
0 / 0

[JIRA] (HHH-16096) Passing an ExtendedBeanManager which is notified too late leads to initialization error

by Vedran Prišćan (JIRA)

Vedran Prišćan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=63d101b... ) *commented* on HHH-16096 ( https://hibernate.atlassian.net/browse/HHH-16096?atlOrigin=eyJpIjoiZWY2Mz... ) Re: Passing an ExtendedBeanManager which is notified too late leads to initialization error ( https://hibernate.atlassian.net/browse/HHH-16096?atlOrigin=eyJpIjoiZWY2Mz... ) I did write a test in the commit: https://github.com/hibernate/hibernate-orm/pull/6018/commits/69ea77de8c43... ( https://github.com/hibernate/hibernate-orm/pull/6018/commits/69ea77de8c43... ) I agree that with your solution this should not happen, but for consistency with BeanImpl there should also be a null check in NamedBeanImpl. Or we can remove both null checks if it can never happen anymore, but I prefer there is one. ( https://hibernate.atlassian.net/browse/HHH-16096#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16096#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#100214- sha1:3d33cb1 )

1 year, 7 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 January 2023