spectacles-ci
Don't run dimension-level queries from passing chunks
In the current state of the SQL validator, Spectacles breaks up Explore-level queries into N chunks of M dimensions, where M is configured via the --chunk-size arg, with a default of 500 queries per chunk.
Chunk size was mainly implemented to solve the query character length limit occasionally encountered by large Looker instances with large Explores (many dimensions).
When set to the default value, a chunk size of 500 essentially imitates the existing functionality of one query per Explore, except in less common cases where Explores have more than 500 dimensions.
If we skipped over querying dimensions from passing chunks, in many cases, it might be advantageous for users to choose a smaller chunk size, because it would allow us to break up an explore into smaller pieces to test. In the end, something like binary search is probably the right algorithm to pursue for performance optimization (see #147).
