cnauroth commented on pull request #3463: URL: https://github.com/apache/hadoop/pull/3463#issuecomment-932531983
My only other thought is that this sort of logic is the kind of thing that should eventually make its way over to using `PathCapabilities`. For complete accuracy though, the HDFS client implementation would need its `hasPathCapability` implementation to have knowledge of whether or not the remote NameNode has xattrs enabled. Considering federation, you might even have different namespaces enabled or disabled, so the final answer is dependent on the path presented by the caller. We could avoid that complexity if we removed the configuration property for disabling xattrs. (It's a stable feature at this point.) That would be a backward-incompatible change though. I've tried more brainstorming on this, and unfortunately, I can't think of a solution with high confidence in guaranteeing backward compatibility. We've focused discussion on xattrs so far, but there is similar logic for ACLs too that is susceptible to the same problems. -- 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]
