Closed
Description
The current behaviour of the DefaultJobParametersConverter
has been confusing in many situations:
- The way to specify parameter types with the
parameter(type)=value
notation is not friendly to command line arguments and environment variables - The way to specify identifying / non identifying job parameters with
+
/-
prefixes is not friendly with Spring Boot
While it is possible to provide a custom JobParametersConverter
and set it on the CommandLineJobRunner
or JobOperator
, I believe the default behaviour should be reviewed for a better getting started experience for batch users and a better integration with Spring Boot. Since this could be a breaking change, I see v5 as a good opportunity to revisit this part of the framework.
References:
- https://stackoverflow.com/questions/66302293/spring-batch-job-param-always-show-zsh-no-matches-found
- Task status is Unknown when using exec as entry point style spring-attic/spring-cloud-dataflow#4291
- Add a property to all for Batch JobParameters to enable configuration via environment variables spring-boot#23411
Related issues: