Skip to content
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

Update rules for when discover_schema returns http error codes #1821

Merged
merged 1 commit into from
Jan 25, 2021

Conversation

cgardens
Copy link
Contributor

  • Previously if the job failed at all the API would return a 4XX or 500. This prevented the UI from being able to display logs from the failed job.

  • Instead, if the underlying job fails the API will still return a 200. The schema field will be empty however and the consumer must check the jobInfo.status field to determine if the job succeeded or not.

  • Will still return 422 on invalid inputs.

* Previously if the job failed at all the API would return a 4XX or 500. This prevented the UI from being able to display logs from the failed job.

* Instead, if the underlying job fails the API will still return a 200. The schema field will be empty however and the consumer must check the jobInfo.status field to determine if the job succeeded or not.

* Will still return 422 on invalid inputs.
@cgardens cgardens merged commit e77b18c into master Jan 25, 2021
@cgardens cgardens deleted the cgardens/discover_error_codes branch January 25, 2021 19:17
@jamakase
Copy link
Contributor

closes #1697

@jamakase jamakase linked an issue Jan 25, 2021 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When Discover Schema fails we should show logs
2 participants