RussellSpitzer commented on issue #12943: URL: https://github.com/apache/iceberg/issues/12943#issuecomment-2855108368
> > Is the goal here to be able to build an identity transform but name it differently than the source column? > > If source columns can be renamed, then this situation will happen if you try to create a PartitionSpec for the table after the column was renamed. Column names are mutable, but transform names are not, as far as I can tell. I'm not sure I see the issue here? With the current API I get a transform named identically to the source column as it is set which sounds correct. We could rename the transforms as we rename their identity source columns if we want to but i'm not sure why a user would want/need to explicitly create an identity transform with a different name. I think if we have a strong use case we could open it up. > In any case, why is the access control different for identity and every other transform type? I think again because there isn't really a use case for having the name different from a user prospective. We could open it up but i'm not sure what we would get from allowing that? -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
