-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE in HqlQueryTransformer.isSubquery for UPDATE HQL #3649
Comments
Thank you @dforrest-es for reporting and analysis. |
The issue is also reproducible when switching from Spring Boot 3.3.4 to 3.3.5. If using the following pom in the example project from above:
When switching back to 3.3.4 the app starts up properly. In my application I encountered the same issue with a @query annotation:
|
Many of our services also had failed builds when updating to Spring Boot 3.3.5 due to this bug. The workaround is to put this in your POM 's properties: <spring-data-bom.version>2024.0.4</spring-data-bom.version> this will use the previous version of spring-data-jpa that works. |
Thanks for a quick fix @mp911de & @christophstrobl! |
Is there any ETA of releasing that fix? |
We do, check out the Release Calender for most recent schedule updates in accordance with the assigned milestone. |
With 3.2.11, repository initialization fails with
Issue is very similar to #2977 but for update clauses:
Entity:
Repository:
Reproducer:
demo.zip
Extract and run ./mvnw spring-boot:run to observe the exception.
In the pom.xml, change the spring-data-jpa.version from 3.2.11 to 3.2.10 and run again, now it works.
My investigation:
Specifically, this change causes
HqlQueryTransformer#isSubquery(ParserRuleContext)
to be run for update clauses & likely needs the same fix from #2977 applied forHqlParser.UpdateStatementContext
(see commit 6b9d3e2)Wrokaround:
Removing the
AS
from the table alias bypass this error.The text was updated successfully, but these errors were encountered: