jfz commented on PR #5230:
URL: https://github.com/apache/iceberg/pull/5230#issuecomment-1195009103

   @rdblue thanks for looking into this and the insights!
   
   > They are intended for information to configure reading or writing a table.
   
   Time to evolve? :) I feel this can be useful and unlock new use cases that 
require stateful/transactional update to any table specific meta info.
   
   > implementation challenges, e.g. REST Cagalog
   
   I think this can be a generic challenge for passing any sort of 
transformation to server that's worth looking into, a quick thought would be 
either serialize/deserialize or predefined transforms like `partition 
transforms`. Or we can choose not to support in REST Catalog to start with.
   
   > using a prefix instead of a single option
   
   I think it will reduce but not eliminate the chance of overwrite on commit 
conflicts.
   


-- 
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]

Reply via email to