-
Notifications
You must be signed in to change notification settings - Fork 124
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
Upgrade to Apache Iceberg 1.6.1 #7
Conversation
@RussellSpitzer afair some tests were failing, I gonna fix that 😄 |
This could be dangerous based on how much Polaris depends on Iceberg and the changes between iceberg 1.5 and 1.6. I'd suggest people who are familiar with the Polaris tests coverage to take a look. Just in case we hit any issue, esp. sedes related ones. |
@flyrain I'm investigating, I think I found the problem 😄 |
* Add initial integration tests * Add gradle workflow in github * Fixed Dockerfile to create default-realm dir for sqlite * Add docker-compose and Dockerfile for regtest * Docker build in ci * Fix context in docker-compose file * Update regtest to work locally and in docker * Fix dockerfile to run gradle build * Add .keep file for output directory
<!-- Please describe your change here and remove this comment --> This PR implements a basic CLI for Polaris, supporting simple commands like: ``` polaris catalogs list polaris catalogs create --type --storage-type s3 --default-base-location s3://my-bucket --role-arn ${ARN} polaris principals update emaynard --property foo=bar --property e=mc2 polaris privileges --catalog my_cat --catalog-role my_role namespace grant --namespace a.b.c TABLE_READ_DATA polaris privileges --catalog my_cat --catalog-role my_role table revoke --namespace a.b.c --table t1 TABLE_READ_DATA ``` See [this doc](https://docs.google.com/document/d/1yug1YGcNASmiOyZCJBoWXbsF5KDtO-IWQq0LLvOADzg/edit) for a full list of supported operations. ## Pre-review checklist - [ ] I attest that this change meets the bar for low risk without security requirements as defined in the [Accelerated Risk Assessment Criteria](https://developer-handbook.m1.us-west-2.aws.app.snowflake.com/docs/reference/security-review/accelerated-risk-assessment/#eligibility) and I have taken the [Risk Assessment Training in Workday](https://wd5.myworkday.com/snowflake/learning/course/6c613806284a1001f111fedf3e4e0000). - Checking this checkbox is mandatory if using the [Accelerated Risk Assessment](https://developer-handbook.m1.us-west-2.aws.app.snowflake.com/docs/reference/security-review/accelerated-risk-assessment/) to risk assess the changes in this Pull Request. - If this change does not meet the bar for low risk without security requirements (as confirmed by the peer reviewers of this pull request) then a [formal Risk Assessment](https://developer-handbook.m1.us-west-2.aws.app.snowflake.com/docs/reference/security-review/risk-assessment/) must be completed. Please note that a formal Risk Assessment will require you to spend extra time performing a security review for this change. Please account for this extra time earlier rather than later to avoid unnecessary delays in the release process. - [ ] This change has code coverage for the new code added
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I'm resuming my work on this one, also rebasing. |
I found that the tests failure are related to this change in Apache Iceberg:
I suspect it's about the table version. I will update Polaris to deal with this Iceberg fix. |
I confirm commit |
@jbonofre : I believe the test failures in I was thinking of just adding a counter to the method name. We could try and delete old catalogs after each test, but it seems to be too involved for an Iceberg version bump due to emptiness checks on delete. |
@dimas-b it's both. I saw the namespace issue but I can confirm that the default version in table metadata cause tests failure as well. |
hmmm.... I ran that test locally yesterday and it passed with just fixing the catalog name to be unique. |
@dimas-b let me update this PR with the fix (I would love to have your review 😄 ). |
eefd1b6
to
8220c8f
Compare
@dimas-b you were right as the failure was related: it was mixing metadata from different catalog. By isolating catalog, it should be ok now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM :) Thanks, @jbonofre !
CC: @snazy for a binding +1 :) |
Fixes #5