-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Data loss after update to Quarkus 1.10.5 #14201
Comments
cc @Sanne |
@Sanne Any clues on why this could happen? |
I experience the same issue. It occurs if a method that performs the select is |
I managed to create a repro case https://github.com/yntelectual/quarkus-bug-14201 along with a small readme, but it is really weird: there are several ways how to avoid the bug behaviour e.g. removal of a lazy association, removal of attribute in parent class 😱.. so it feel pretty strange. Looking forward to any result. |
Thanks @yntelectual for the reproducer, I'm going to give a look at it. |
@yntelectual Thanks for confirming this issue. I thought I was going crazy. |
Opened a Jira https://hibernate.atlassian.net/browse/HHH-14424, working on it. |
I was running on Quarkus 1.9.1. I recently updated directly to 1.10.5
I started seeing some db entries get wiped out, when accessing a related table.
I have been able to reproduce it in my environment with a simple db read now.
I use postgres, panache, hibernatesearch among other extensions.
It basically boils down to something like
What happens is when I call
Book.findById(
), the data in the corresponding Shop entity gets set to null.I am not sure if there is something wrong, in the way I have written the entity, but this used to work in 1.9
I then took Quarkus v1.10.3
I now get an exception in the same sequence.
Since the transaction fails, I dont have data loss, but looks like something is trying to overwrite the shop entity
Commenting out the Shop entity from Book, causes everything to work ok, in both versions
I have tracked down the change in behaviour to the CRM changes in 1.10.4
I have been able to reproduce this reliably in my environment, but havent been able to create a standalone example.
The text was updated successfully, but these errors were encountered: