nssalian commented on issue #3258: URL: https://github.com/apache/iceberg-rust/issues/3258#issuecomment-5778372244
Re-reading, I want to check to make sure I understand the intent here: is the idea to have a central capability check for whether a type is safe to read/write, and then enforce that at the relevant entry points (scan planning, writers, etc.)? If so, I wonder if read/write alone is enough granularity. For example, a type might support decoding/encoding values correctly but not yet support metrics, predicates, or bounds. Geometry seems like an example where writing the value is safe as long as unsupported bounds are omitted. Would it make sense to model this as capabilities (read, write, metrics, etc.) and have the relevant paths check the capability they require? -- 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]
