smaheshwar-pltr opened a new issue, #3729: URL: https://github.com/apache/iceberg-rust/issues/3729
### Is your feature request related to a problem or challenge? Writers currently have to choose a location generator themselves - the default one, or the object storage one. But that can leave the `write.object-storage.enabled` property ignored, unless writers all handle that caseworking themselves. [Iceberg Java](https://github.com/apache/iceberg/blob/ff854726011fd35d90cdb1390754e28e6ea84b67/core/src/main/java/org/apache/iceberg/LocationProviders.java#L39-L125) on the other hand, as well as some of the other Iceberg language implementations, provide utilities for doing this instead. ### Describe the solution you'd like There are some different approaches - we could change the `DefaultLocationGenerator` to have this property-based caseworking behaviour but that would break existing callers' behaviour (it would also diverge from the reference implementation where there's a similar separation between `DefaultLocationProvider` and the `LocationProviders.locationsFor(...)` factory. An alternative here is a new location generator, constructed via something like `TableLocationGenerator::new(&TableMetadata)`to select the default or object-storage layout from table properties. ### Willingness to contribute I can contribute to this feature independently -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
