Hi, I noticed that Trafodion requires that dfs.namenode.acls.enabled is set to true. The reason for this seems to be a desire to do a set setfacl on hbase/archive.
Is this a true requirement or an embedded best practices? I'm wondering since we're now imposing security policies on the user even if the user has chosen to rely on the traditional POSIX permission model over implementing the extended POSIX ACL model. Also, how does this HDFS configuration flag relate to a user that is using Kerberos? -- Thanks, Gunnar *If you think you can you can, if you think you can't you're right.*
