-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Extend fetchSize support across JPA Item Readers #4506
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
Conversation
...nfrastructure/src/main/java/org/springframework/batch/item/database/JpaCursorItemReader.java
Outdated
Show resolved
Hide resolved
...nfrastructure/src/main/java/org/springframework/batch/item/database/JpaPagingItemReader.java
Outdated
Show resolved
Hide resolved
@baezzys Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
@baezzys Thank you for signing the Contributor License Agreement! |
c6f5df1
to
26314ad
Compare
@baezzys Thank you for the PR! I added an inline comment on how we should address this feature request. Could please take a look? If you agree, please update the PR and it should be good to merge. Thank you upfront. |
@fmbenhassine Thanks for checking out my PR. But I can't seem to find the inline comment you're talking about. Can you point me in the right direction? |
26314ad
to
38649f2
Compare
The JPA reader should not depend on APIs from a specific implementation (ie |
@fmbenhassine Thank you for your review and feedback! I'll update the PR to use |
38649f2
to
c2b5dc4
Compare
Enhanced `JpaCursorItemReader`, `JpaCursorItemReaderBuilder`, `JpaPagingItemReader`, and `JpaPagingItemReaderBuilder` with query hints configuration. The inclusion of query hints in both cursor and paging item readers improves query execution strategies, optimizing performance for complex data retrieval scenarios.
c2b5dc4
to
9d3bb29
Compare
@fmbenhassine I've updated the PR to include a Map<String, Object> hintValues for hints, similar to our approach with query parameters. This change ensures our JPA reader is implementation-agnostic, allowing users to specify provider-supported hints directly. I hope this update aligns with your guidance. Please let me know if there are any further adjustments needed. |
Thank you for the update, LGTM now 👍 Rebased and merged as 5a261fa. Thank you for your contribution! |
Nice work @baezzys ! |
Resolves #4479