NullPointerException in TupleMappingModelExpressible constructor

Description

Queries with tuples composed of attributes coming from subqueries, such as:

trigger a NullPointerExcetpion in the constructor of the TupleMappingModelExpressible class when resolving the tuple part (fromSubquery.name, fromSubquery.color).

Attachments

Linked issues

is followed up by

HHH-17803

NPE in TupleMappingModelExpressible constructor when enum is used in "in" clause tuple within subquery

relates to

HHH-17701

@Converter ignored for attributes used in tuples leading to NullPointerException in TupleMappingModelExpressible constructor

Activity

Show:

Yoann Rodière October 21, 2024 at 8:07 AM

Thanks for reaching out. This bug was supposedly fixed in 6.4.0.CR1. If you’re still having problems on more recent versions, please open a separate bug report with a reproducer, preferably on 6.6 since 6.5 is not longer maintained.

LEROUX Erwan (P) October 18, 2024 at 6:46 PM

The bug seems to be present in the 6.5.2 version as well

Yoann Rodière April 24, 2024 at 6:43 AM

Also, the Quarkus upgrade was merged just now, and is ready to be backported:

Marco Belladelli April 23, 2024 at 9:02 PM

The fix for that issue is included in 6.4.5, as the fix version of the Jira says. That version was released today.

Michael Weber April 23, 2024 at 8:59 PM

thanks for the update and your continued assistance

I just wanted to make soem thoughts/comments regarding “we were waiting for the final version of 6.5“. I think the intermediate bugfixes like 6.4.5 are crucial, regardless of imminent minor versions, because it’s not always easy to upgrade versions with integrated frameworks. For example, I use Quarkus, and with Quarkus 3.4 (which uses Hibernate 6.2), I cannot force the Hibernate version up to 6.4 to utilize this fix because there are breakages in the framework, so I was not able to get this bugfix until Quarkus was upgraded to support 6.4 (in Quarkus 3.7). But now because of , I still can’t even upgrade to Hibernate 6.4/Quarkus 3.7+. So if the fix for the latter issue only went into Hibernate 6.5, I may have to wait even longer for it because it needs to be integrated into the next version of the Quarkus framework.