Skip to content

Outdated contract of APIs accepting job parameters as String #4301

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.

Sign up for GitHub

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

Jump to bottom
Closed
fmbenhassine opened this issue Feb 16, 2023 · 0 comments
Closed

Outdated contract of APIs accepting job parameters as String #4301

fmbenhassine opened this issue Feb 16, 2023 · 0 comments
Labels
in: core in: test type: bug
Milestone
5.0.1

Comments

@fmbenhassine
Copy link
Contributor

fmbenhassine commented Feb 16, 2023 •
edited
Loading

JobOperator#start and MetaDataInstanceFactory#createJobExecution expect job parameters to be passed as a single string which is either a comma separated or a new line separated key/value pairs.

The comma separated format is incompatible with the new format introduced in v5 (see #3960) . PropertiesConverter (which is the utility used behind the scene by those APIs) should be updated to only support new line delimited key/value pairs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
in: core in: test type: bug
Projects
None yet
Milestone
5.0.1
Development

No branches or pull requests
1 participant
@fmbenhassine