-
Notifications
You must be signed in to change notification settings - Fork 590
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
feat(iceberg): use native glue impl for iceberg source #18106
Conversation
let catalog = iceberg_catalog_glue::GlueCatalog::new(config).await?; | ||
Ok(Arc::new(catalog)) | ||
} | ||
catalog_type if catalog_type == "hive" || catalog_type == "jdbc" => { |
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.
Are we going to change other types too later?
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.
Yes, I am trying to change the hive
catalog later by iceberg-catalog-hms
. But the jdbc
one can't be changed with iceberg v0.3.0
meta panic after aws-config and aws-runtime upgrading
|
name = "aws-sdk-s3" | ||
version = "1.1.0" | ||
version = "1.17.0" | ||
source = "registry+https://github.com/rust-lang/crates.io-index" | ||
checksum = "62d240c8c3e3663cd278e47702bbd2566203362d93b51d95575d7b2e0c265e99" | ||
checksum = "93d35d39379445970fc3e4ddf7559fff2c32935ce0b279f9cb27080d6b7c6d94" |
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.
aws-sdk-s3
will be upgraded to 1.17.0
As I know, this PR #18011 has been merged which means we will use opendal by default for object store. |
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.