viirya commented on issue #26956: [SPARK-30312][SQL] Preserve path permission and acl when truncate table URL: https://github.com/apache/spark/pull/26956#issuecomment-572761320 @dongjoon-hyun Thanks for notifying me this. This looks worth back-porting, though it is not a regression as we never preserve permission/ACLs before, so my opinion is not strong too. @srowen I think it depends on case by case. Internally we have seen performance issue on sequential RPC calls to namenode (not truncate table, but file commit ops), so my first thought is not to do it again here. Our Spark users reported that the custom ACLs they set were lost after truncating table. There could be non default ACLs setting on the table path we don't like to lose it just because truncating table.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
