mapleFU commented on issue #2: URL: https://github.com/apache/iceberg-cpp/issues/2#issuecomment-2522235925
This seems like a two-part of work, like: 1. Catalog layer, read/write the catalog. For write, would something like conflict detect being used? Expression and types might be used for metadata pruning and planning? 2. Table Reading layer, which allowing reading the file with puffin, deletion vector, and base data file. For positional delete things would be simpler, but for equality delete things would be a bit tricky. This would be something like `::arrow::dataset` module in Arrow C++, more over, if type for iceberg is separated, we need whether mapping the types to arrow's type, or rewriting the expr / pruning works... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
