fix: removed EntityManager.clear() from GraphQLJpaQueryDataFetcher #192
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes calling EntityManager.clear() inside GraphQLJpaQueryDataFetcher.get() that causes runtime NPE in Hibernate in order to fix #191
The
EntityManager.clear()
has been added in this commit: 83c5a84 because of the mentioned problem: #96 (comment)The provided test case cannot reproduce the issue anymore: 9e5002b
Calling clear method seems to be very invasive. There are already hints provided for Hibernate not to cache any results in memory:
graphql-jpa-query/graphql-jpa-query-schema/src/main/java/com/introproventures/graphql/jpa/query/schema/impl/GraphQLJpaQueryDataFetcher.java
Line 133 in 7ce947d
Also, this problem could be still relevant in Hibernate versions before 5.3.10. The users may need to call
EntityManager.clear()
before execution of the query manually if needed.