-
Notifications
You must be signed in to change notification settings - Fork 41k
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
Group JDBC-related batch properties beneath spring.batch.jdbc #25053
Comments
@benas, @wilkinsona Thanks |
Thanks for the offer, @chaundhyan. That would be great. We'll need to deprecate the existing properties (using |
@benas @wilkinsona : I've had done the changes. Would you like to review it over my repo? Shall i raise the PR, if yes then into which branch? If any suggestion, please do let me know. Also there exists 3 test cases which are failing while doing Same way other are failing. Please suggest. Thanks |
@chaundhyan Yes, please do raise a PR against the master branch. One change that I would make to your proposal is to nest |
Closing in favor of PR #25316 |
As of v2.4.2, JDBC-related properties for batch are under
spring.batch
, unlike quartz, session and integration where those properties are underspring.xxx.jdbc
.After discussing this with @wilkinsona , I understand that this is because JDBC is currently the only store option for batch. However, I think it would be better to group those properties beneath
spring.batch.jdbc
for 1) naming consistency and 2) to pave the way for other storage options for batch in the future (We have indeed a feature request to support a non-jdbc job repository implementation, see spring-projects/spring-batch#877 which we might consider in the next major release).The text was updated successfully, but these errors were encountered: