-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Core: Relocate parquet to core #11716
Conversation
Already we have a PR and issue tracker for the same
Since, |
is there anything left in |
@nastra: He kept dummy module for compatibility. But I think it can be removed as mentioned in #11716 (comment) My PR has end to end work, I can revive it. |
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the [email protected] list. Thank you for your contributions. |
@danielcweeks: I have updated my old PR as per latest code. Please take a look. Maybe this can go in for 1.8.0 too. |
Aah, I got the same Spark smoke test failure too. Let me debug this. |
Closing in favor of #12060 |
This PR relocates the parquet implementation from the
iceberg-parquet
project toiceberg-core
so that parquet can be used as part of metadata operations.The project and artifacts are left so that dependencies still resolve and we can deprecate in a future release.