MaxNevermind commented on PR #3036: URL: https://github.com/apache/parquet-java/pull/3036#issuecomment-2434342726
> What is your use case? We have a large base dataset which is split into multiple versions at the end of the flow. Those final datasets have majority of columns overlapping but some columns are dropped & some columns are renamed. Similar thing can be achieved by multiple HMS views on the top of unified base HMS table but it is not always possible, for example if different users are supposed to have access just to a single version of a dataset, it is hard to achieve that with HMS views without giving access to users to that underlying unified table. > Do you need reordering fields in the future? In our case we don't care about column ordering. > How does renaming work with other features, including join, mask, and encrypt? mask - it is not supported as it seems meaningless to rename a column that is dropped join - I planned to support it, so the column could be joined and then renamed if needed encrypt - I planned to support it, so the column can be encrypted and renamed if needed -- 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]
