feat: Add plain "status" field to the JobResponse#1497
Merged
milenkovicm merged 1 commit intoapache:mainfrom Mar 10, 2026
Merged
feat: Add plain "status" field to the JobResponse#1497milenkovicm merged 1 commit intoapache:mainfrom
milenkovicm merged 1 commit intoapache:mainfrom
Conversation
The old "job_status" is more like a status description with some extra information. The plain "status" field just gives one of: Running, Queued, Completed or Failed
milenkovicm
approved these changes
Mar 10, 2026
Contributor
milenkovicm
left a comment
milenkovicm
left a comment
There was a problem hiding this comment.
this looks like a backward compatible change, you're adding new field (or im missing something), anyway its good change thanks
Contributor
|
merge whenever ready @martin-g |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Closes #351.
Rationale for this change
The old "job_status" is more like a status description with some extra information.
The plain "status" field just gives one of: Running, Queued, Completed or Failed
What changes are included in this PR?
The JobResponse entity now includes a
"status"field which value is just the status name without any extra details. One of: "Running", "Queued", "Completed" or "Failed".Are there any user-facing changes?
A new field is added to the JobResponse JSON in a backward compatible way