BlakeOrth commented on issue #172: URL: https://github.com/apache/iceberg-rust/issues/172#issuecomment-2474390321
Wow, I did not expect my comment digging up a nearly year old issue to result in this much discussion! I likely have less skin in the game than any of the maintainers here, but I think @gruuya and @JanKaul's most recent comments mirror what I personally had in mind. That being said, I think pretty much any of the proposed solutions would allow users to solve the underlying problem here. I would also like to highlight @tustvold's comment: > It would also more closely mirror the java APIs which I understand is a goal here. Edit: That being said if providing an idiomatic API for Rust users is more important than matching the Java APIs I can make alternative suggestions along those lines. I personally think having an API that's idiomatic ends up being very important for long-term usability, and in turn the long-term health, of a given package. Maintaining similar units of abstraction, and the names of those units of abstraction, across a multi-language ecosystem such as arrow/iceberg/etc. is important for developer familiarity. However, I have personally seen multiple instances where the community has entirely re-implemented a package because the original API was mirrored from another language and was not ergonomic to use. -- 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
