The Looker API returns the status expired for certain queries. However, sometimes it's a false alarm as the query eventually resolves itself to a completed status.
This change waits up to 30 seconds for that resolution to happen. If the query's status is still expired at that point, it puts the query back on the queue to be retried. After 2 retries it gives up and adds an error to the Explore.
Type of change
[x] Bug fix (fixes an issue)
[ ] New feature (adds functionality)
Related issues
Closes #111.
Checklists
Security
[x] Security impact of change has been considered
[x] Code follows security best practices and guidelines
Code review
[x] Pull request has a descriptive title and context useful to a reviewer
This PR still needs tests. I also need to investigate if a run with both Explore and dimension-level errors will be problematic for printing out in the CLI.
Change description
The Looker API returns the status
expired
for certain queries. However, sometimes it's a false alarm as the query eventually resolves itself to a completed status.This change waits up to 30 seconds for that resolution to happen. If the query's status is still
expired
at that point, it puts the query back on the queue to be retried. After 2 retries it gives up and adds an error to the Explore.Type of change
Related issues
Closes #111.
Checklists
Security
Code review