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

SNOW-1700248 Revert turning native arrow boolean primitives lowercase #1906

Conversation

sfc-gh-mkubik
Copy link
Contributor

@sfc-gh-mkubik sfc-gh-mkubik commented Sep 30, 2024

Revert turning native arrow boolean primitives lowercase (changed in PR#1882) to prevent introducing a breaking change.
Structured types' booleans string representation will remain lowercase to preserve JSON-compatibility

Overview

SNOW-1374896
SNOW-1700248

Pre-review self checklist

  • PR branch is updated with all the changes from master branch
  • The code is correctly formatted (run mvn -P check-style validate)
  • New public API is not unnecessary exposed (run mvn verify and inspect target/japicmp/japicmp.html)
  • The pull request name is prefixed with SNOW-XXXX:
  • Code is in compliance with internal logging requirements
  1. Please describe how your code solves the related issue.

I reverted the global boolean case change and implemented a structured type string builder one. Primitive booleans will remain UPPERCASED while booleans within structured types will be lowercased to provide JSON compatibility

…ntroducing a breaking change. Structured types' booleans string representation will remain lowercase to preserve JSON-compatibility
@sfc-gh-mkubik sfc-gh-mkubik changed the title Revert turning native arrow boolean primitives lowercase SNOW-1700248 Revert turning native arrow boolean primitives lowercase Sep 30, 2024
@sfc-gh-mkubik sfc-gh-mkubik marked this pull request as ready for review September 30, 2024 13:36
@sfc-gh-mkubik sfc-gh-mkubik requested a review from a team as a code owner September 30, 2024 13:36
@sfc-gh-mgol
Copy link

Do you guys have plans on how to improve the release process to avoid such breaking changes in the future?

@sfc-gh-mkubik
Copy link
Contributor Author

sfc-gh-mkubik commented Sep 30, 2024

Do you guys have plans on how to improve the release process to avoid such breaking changes in the future?

In terms of release process I believe the BPTP validation does that and there won't be a new version of the driver released with such changes. It'd make sense to include similar checks on the PRs to verify before merging to master.

@sfc-gh-mkubik sfc-gh-mkubik reopened this Sep 30, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Sep 30, 2024
@snowflakedb snowflakedb unlocked this conversation Sep 30, 2024
@sfc-gh-yuliu
Copy link

Please merge this PR. This causes 30+ test failures every run for us.

Copy link
Collaborator

@sfc-gh-astachowski sfc-gh-astachowski left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@sfc-gh-pmotacki sfc-gh-pmotacki left a comment

Choose a reason for hiding this comment

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

LGTM

@sfc-gh-mkubik sfc-gh-mkubik merged commit 06ca752 into master Oct 1, 2024
244 of 278 checks passed
@sfc-gh-mkubik sfc-gh-mkubik deleted the SNOW-1374896-fix-failing-bptp-pipeline-change-boolean-string-case branch October 1, 2024 06:56
@github-actions github-actions bot locked and limited conversation to collaborators Oct 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants