Simple update by Named Query without "WHERE" Statement results in "unexpected end of subtree" errors
Description
After upgrading hibernate to current 5.4.XX Version, I observed in our logs Some “antlr.NoViableAltException: unexpected end of subtree“.
After Investigation, what went wrong, I came to the conclusion, that something broke in Hibernate.
It still works in Hibernate 5.4.20, all newer versions are affected
I assume that it was caused by CommitId “9dd2d94a“ (“HHH-14153 further optimization for single-table HQL update”) because I could reproduce behavior with unittest Case and before this commit it workred fine.
In Attachement, you can find my written test case and the test results of it.
Fixed in v6, and there is an easy workaround for it in v5.
Jan Schatteman September 30, 2022 at 7:33 PM
Thanks for your test case, I have included it in our test suite, and could also reproduce the stack trace. However, since it’s limited to a logged message I would suggest as a workaround that you deactivate the org.hibernate.hql.internal.ast.ErrorTracker logger.
After upgrading hibernate to current 5.4.XX Version, I observed in our logs Some “antlr.NoViableAltException: unexpected end of subtree“.
After Investigation, what went wrong, I came to the conclusion, that something broke in Hibernate.
It still works in Hibernate 5.4.20, all newer versions are affected
I assume that it was caused by CommitId “9dd2d94a“ (“HHH-14153 further optimization for single-table HQL update”) because I could reproduce behavior with unittest Case and before this commit it workred fine.
In Attachement, you can find my written test case and the test results of it.