Dylan Baker
Dylan Baker
**Are you a current Fivetran customer?** Let's say yes. **What change(s) does this PR introduce?** This PR gives users the option to select whether they would like to use the...
When runs have lots of errors and run long as a result, it would be really useful to be able to easily find out which explores have failed. We should...
Users and customers sometimes ask why runs are taking longer than they expect. Often, this is due to bad SQL performance, which they can analyze with the query profiler. However,...
## Change description This change adds scripts to check that two different branches produce the same results. ## Type of change - [ ] Bug fix (fixes an issue) -...
This issue arises in two different scenarios: * In incremental mode, if no explores are found to be tested, we still enter the branch manager [here](https://github.com/spectacles-ci/spectacles/blob/master/spectacles/runner.py#L345-L346) * In non-fail-fast mode,...
When trying to analyse the performance of Spectacles runs, it would be useful to know how long each API call is taking. Some take significantly longer than others, i.e. the...
If a column is given the wrong `type`, it is possible it will still run in a query, but fail when you try to filter on it. i.e. if you...
There are scenarios, such as when a whole table doesn't exist, that every (or almost every) dimension in a view will produce effectively the same SQL error (which is that...
This isn't so much a bug with Spectacles as it is an issue with Looker that we want to track. Often, in order to test Looker with changes to code...
It would be useful to add additional context to the files that store the failing SQL. As an example: ```sql /* The Google BigQuery Standard SQL database encountered an error...