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

fix(go/adbc/driver/snowflake): Make SHOW WAREHOUSES test less flaky #1494

Merged
merged 1 commit into from
Jan 27, 2024

Conversation

joellubi
Copy link
Member

Minor fix to a test that has been breaking each time Snowflake added a new field to the result of a SHOW WAREHOUSES query.

Previously we asserted the number of columns, but this number has been changing. Instead of completely removing this part of the test, we can assert the columns we know currently should be present and expect that Snowflake won't make breaking changes to the schema by removing columns. The specific contents of the schema are not relevant to the original purpose of the test anyway, so it should be fine if the actual schema continues to grow beyond what is asserted here.

@github-actions github-actions bot added this to the ADBC Libraries 0.10.0 milestone Jan 27, 2024
@joellubi joellubi changed the title feat(go/adbc/driver/snowflake): Make SHOW WAREHOUSES test less flaky fix(go/adbc/driver/snowflake): Make SHOW WAREHOUSES test less flaky Jan 27, 2024
@joellubi joellubi marked this pull request as ready for review January 27, 2024 01:10
Copy link
Member

@zeroshade zeroshade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lidavidm lidavidm merged commit fabbec8 into apache:main Jan 27, 2024
34 checks passed
soumyadsanyal pushed a commit to soumyadsanyal/arrow-adbc that referenced this pull request Jan 31, 2024
…pache#1494)

Minor fix to a test that has been breaking each time Snowflake added a
new field to the result of a `SHOW WAREHOUSES` query.

Previously we asserted the number of columns, but this number has been
changing. Instead of completely removing this part of the test, we can
assert the columns we know currently should be present and expect that
Snowflake won't make breaking changes to the schema by removing columns.
The specific contents of the schema are not relevant to the original
purpose of the test anyway, so it should be fine if the actual schema
continues to grow beyond what is asserted here.
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.

3 participants