Skip to content
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

Allow JpaItemWriter to support persist rather than merge for improved performance. [BATCH-2462] #1140

Closed
spring-projects-issues opened this issue Dec 23, 2015 · 0 comments

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Dec 23, 2015

Chris Cranford opened BATCH-2462 and commented

The current implementation of JpaItemWriter uses the merge function in order to write items to the JPA persistence context. This makes sense when the existence state of a record is unknown or is never considered an insert.

But there are business cases where it is known that the record being provided is always considered an insert and the writer's performance could significantly be improved by allowing the JpaItemWriter to support using persist for these use cases.


Affects: 3.0.6

Referenced from: pull request #399, and commits 229fed4

Backported to: 4.2.0.M3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants