Chris
Chris
Hmmm.. need to think on this one. There's also the concept of an AnyType, which is semantically *slightly* different, but is more in line with what most type systems have....
Gotcha, this totally makes sense as a use case. I'm thinking through implementation approaches. I am hesitant to modify the type system for this; it feels more like a valid...
@mjperrone @adrianisk K, let's move forward by adding UnknownType in types.py. The converters should all be updated to return UnknownType instead of raising an exception. I think we can skip...
This turns out to be really non-trivial. Protobuf's name resolution rules are a real mess. https://github.com/bufbuild/buf/issues/314 https://github.com/protocolbuffers/protobuf/issues/6296 Here are some tests that should work: ```python def test_protobuf_converter_nested_types(): protobuf_schema = """...
Make sure to enable the test_cli.py and test_gateway.py integration tests for protobuf schemas once this is done.
I like all your suggestions. I'll incorporate them. Regarding the third test semantic, what I was trying to emphasize was that a single test could validate both avsc -> Recap...
#264 as well.
It does seem that our HiveMetastoreReader can already read from Iceberg using the [HiveCatalog implementation](https://github.com/apache/iceberg/blob/master/hive-metastore/src/main/java/org/apache/iceberg/hive/HiveCatalog.java)
For the REST API, [pyicberg](https://py.iceberg.apache.org/api/) looks nice.