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

[Feature]: Support Iceberg on S3 or other non-hadoop storage system. #1476

Closed
2 tasks done
baiyangtx opened this issue May 26, 2023 · 0 comments · Fixed by #1481
Closed
2 tasks done

[Feature]: Support Iceberg on S3 or other non-hadoop storage system. #1476

baiyangtx opened this issue May 26, 2023 · 0 comments · Fixed by #1481
Labels
type:feature Feature Requests
Milestone

Comments

@baiyangtx
Copy link
Contributor

baiyangtx commented May 26, 2023

Description

Currently, Arctic only supports running within the Hadoop ecosystem, and it cannot be used effectively with other storage types like Glue + S3. We should support more types of storage systems.

Use case/motivation

We should support managing Iceberg tables with Arctic in S3 + Glue scenarios, optimize it for better performance, and enable features like cleaning up orphan files.

Describe the solution

  1. ArcticFileIO interface should be refactored to reduce its strong dependency on Hadoop.
  2. The Optimizer logic needs to be retested to ensure that it supports non-Hadoop systems.
  3. The logic for cleaning orphan files needs to be adapted to non-file system scenarios. In extreme cases where the storage system does not support list operations, this functionality may need to be downgraded or even unavailable.
  4. Due to the fact that cloud object storage is usually billed based on the number of API calls, the logic of the optimizer checker needs to be adjusted to avoid generating unnecessary costs from frequent checks.

Related issues

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature Feature Requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant