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

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=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:3d33cb1 )