kevinjqliu commented on issue #538:
URL: https://github.com/apache/iceberg-rust/issues/538#issuecomment-2332259085
Looks like @sungwy already started by exposing Transforms in #556
I'll take a stab at exposing the Catalogs, see
https://github.com/apache/iceberg-rust/pull/534#issuecom
kevinjqliu commented on issue #538:
URL: https://github.com/apache/iceberg-rust/issues/538#issuecomment-2293241186
@Xuanwo very cool! looking forward to it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abov
Xuanwo commented on issue #538:
URL: https://github.com/apache/iceberg-rust/issues/538#issuecomment-2292972984
Hi, @kevinjqliu, I'm sorry for blocking your innovation this way.
I've been a bit busy recently, but I plan to create something that really
works next week. For instance, re
kevinjqliu commented on issue #538:
URL: https://github.com/apache/iceberg-rust/issues/538#issuecomment-2290124979
> Does pyiceberg provide an interface that we can integrate with?
Yes, there is a `py-catalog-impl` configuration that will try to load a
given classpath.
([documentatio
liurenjie1024 commented on issue #538:
URL: https://github.com/apache/iceberg-rust/issues/538#issuecomment-2289025670
I think it's definitely possible since `PyIceberg` is `Catalog` interface is
extensible. I think you need to start with pyo3 first to understand how it
works.
--
This is
Xuanwo commented on issue #538:
URL: https://github.com/apache/iceberg-rust/issues/538#issuecomment-2288443167
> I'm wondering if there's also a way to create an integration for a
pluggable catalog, based on the in-memory catalog implementation in #475.
I believe this should also be p
kevinjqliu opened a new issue, #538:
URL: https://github.com/apache/iceberg-rust/issues/538
After establishing #518, I want to start the conversation to create the
first integration between PyIceberg and iceberg-rust.
As discussed in the dev list, we want to create an integration based o
