Given these classes:
I query one user with the entitygraph "User.findByLogin" as FetchGraph, the profile attribute is eagerly loaded as expected.
The issue is that profile.lastModifier is also eagerly loaded.
I think that it profile.lastModifier should respect the default Profile graph and then be Lazy loaded.
Note: I also tried to define an empty Profile subgraph in "User.findByLogin" without effect. profile.lastModifier is still eagearly loaded.
Isn't this a duplicate of ? (which doesn't make it better)
This bug report does not indicate that the reported issue affects version 5.x. Versions prior to 5.x are no longer maintained. It would be a great help to the Hibernate team and community for someone to verify that the reported issue still affects version 5.x. If so, please add the 5.x version that you verified with to the list of affected-versions and attach the (preferably SSCCE) test case you used to do the verification to the report; from there the issues will be looked at during our triage meetings.
For details, see http://in.relation.to/2015/10/27/great-jira-cleanup-2015/
This issue can be closed.
In fact the behaviour seems normal since the object accused of eager loading was already cached in the session du to a prior query.
Thanks for verifying!