kbendick commented on issue #4251: URL: https://github.com/apache/iceberg/issues/4251#issuecomment-1154148268
> > Can you provide a user side example of your idea @yittg? I want to make sure I understand it fully. > > This feature is not required for my personal scenario. In our platform, the metadata is not managed by Flink SQL, so I have no example about this though. > > This issue was primarily intended to initiate a discussion with some preliminary idea. Fully understood. I’m glad this discussion is coming up. I think a few people have given a few different ideas, and I think that some combination of them will likely wind up being best. For example, I really like @wuwenchi’s idea of using UDFs for transform functions vs relying on the column names. One concern with column names is that then would break behavior for users who already have fields with those names (eg they’ve got a data field called ts_month that isn’t intended as a partition transform). I know generally speaking that’s how partition transform fields wind up being named, but we don’t rely on the name but the `PartitionSpec` and associated `PartitionField`s and users are free to rename the partition columns as they choose. But I’m glad this is being brought up. Possibly as the next community sync this can be brought up and then a small working group or anybody interested could come to some design meetings? Throwing that out there as a consideration. Appreciate your taking the time to propose this @yittg (as well as work done by @wuwenchi @hililiwei and others that I apologize if I missed). -- 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]
