c-thiel opened a new issue, #599: URL: https://github.com/apache/iceberg-rust/issues/599
We currently have property names scattered around the crate. If a property needs to be used, it typically needs to be parsed from string first. This is a potentially falling operation that should be done on load. Also defaults are hard to maintain as we don't have a type holding the property key, a type safe value and its default. For our iceberg catalog, we are currently using a system inspired by http's [HeaderValue](https://docs.rs/http/latest/http/header/struct.HeaderValue.html), which is type safe and customizable / expandable for properties defined even in downstream crates. It depends heavily on proc-macros to generate their types. We are thinking about polishing what we have, add things like defaults, and PR it to iceberg-rust. As this is quite some work, I want to make sure that everybody agrees that this could be a good way to go forward, or if other preferred ideas are already floating around. Looking forward for your opinion! A very raw reference: https://github.com/hansetag/iceberg-catalog/blob/0a01eaf87f32e7f393f0d8f0d104594171dccfce/crates/iceberg-ext/src/configs/mod.rs#L12 -- 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.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
