wgtmac commented on issue #2: URL: https://github.com/apache/iceberg-cpp/issues/2#issuecomment-2523303832
> The FileIO is designed to avoid certain operations (move/list/etc), and it only does a few things (read, create, and delete). If wrap this into an abstraction, that would work just as well. I plan to do the following PoC as the next step: - Define `FileIO` related abstraction in the `iceberg-core` library. - Add a `iceberg-arrow` library to provide concrete implementation of `FileIO` backed by `arrow::FileSystem`. This requires to add Arrow as a third-party library. I can use a CMake option `ICEBERG_USE_ARROW` to make it optional. > Another possibility perhaps would be an IO-less abstraction (the Iceberg library tells you what it is waiting for, and you give it what it asks for). Probably more complex to design (and you still perhaps want convenience libraries on top), but definitely more flexible. I'd like to hear more of this. Perhaps a naive example to demonstrate 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 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
