Adding methods for getting redash job id for the query and for tracking redash job status by its id #22
Conversation
This file contains 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
…g redash job status by its id
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed pull request contains a method track_job_status_by_id that allows Redash to complete a query until a valid final status: 3 - SUCCESS, 4 - FAILURE or 5 - CANCELLED ( see https://redash.io/help/user-guide/integrations-and-api/api/ ), instead of setting a timeout. It helps to avoid a case when query timeout specified by the method query_and_wait_result is ( much ) shorter than a timeout for interaction between Redash and selected data source, so the method would return a timeout error before Redash completes query execution.
Usage example: