The requirement is that we plan to have a new keyspace which will hist PII
data and we wanted to see if we can have encrypted ssd then can we find the
new keyspace with PII can be binded to it and no chanhes would required to
current keyspaces.
On Tuesday, July 17, 2018, Rahul Singh wrote:
> Wha
What’s the goal, Abdul? Is it for security reasons or for organizational
reasons. You could try prefixing / suffixing the keyspace names if its for
organizational reasons (For now) if you don’t want to do the manual management
of mounts as Anthony suggested .
--
Rahul Singh
rahul.si...@anant.us
Hi Abdul,
There is no mechanism offered in Cassandra to bind a keyspace (when
created) to specific filesystem or directory. If multiple filesystems or
directories are specified in the data_file_directories property in the
*cassandra.yaml* then Cassandra will attempt to evenly distribute data from
Hi
Can we bind or specify while creating keyspace to bind to specific
filesystem or directory for writing?
I see we can split data on multiple filesystems but can we decide while
fileystem a particular keyspace can read and write?
Hi
Can we bind or specify while creating keyspace to bind to specific
filesystem or directory for writing?
I see we can split data on multiple filesystems but can we decide while
fileystem a particular keyspace can read and write?
