of reference, my understanding on HDFS
multi-tenancy and federation is that for multi-tenancy what we could do is
use file/folder permissions (u,g,o) and ACL's. Or we could dedicate a
namespace per tenant. The issue here is that a namenode (active namenode,
passive namenode and secondary
. Can someone from namespace A1, access the datanode's data in
anyway (hacking) belonging to namespace B1. If not how is it handled?
After going through a lot of reference, my understanding on HDFS
multi-tenancy and federation is that for multi-tenancy what we could do is
use file/folder
of reference, my understanding on HDFS
multi-tenancy and federation is that for multi-tenancy what we could do is
use file/folder permissions (u,g,o) and ACL's. Or we could dedicate a
namespace per tenant. The issue here is that a namenode (active namenode,
passive namenode and secondary namenode) has
. There are two
namenodes A /namespace A1 and namenode B/namespace B1, and have 3
datanodes. Can someone from namespace A1, access the datanode's data in
anyway (hacking) belonging to namespace B1. If not how is it handled?
After going through a lot of reference, my understanding on HDFS
multi
3
datanodes. Can someone from namespace A1, access the datanode's data in
anyway (hacking) belonging to namespace B1. If not how is it handled?
After going through a lot of reference, my understanding on HDFS
multi-tenancy and federation is that for multi-tenancy what we could do is
use file
