Thanks Sam, that's what i was looking for good to know it's in pipeline
Regards
Pranay
On Thu, Apr 19, 2018 at 4:23 AM, Sam Tunnicliffe wrote:
> https://issues.apache.org/jira/browse/CASSANDRA-13985 is probably what
> you're looking for here
>
> Thanks,
> Sam
>
> On 10 April 2018 at 11:55, Rah
https://issues.apache.org/jira/browse/CASSANDRA-13985 is probably what
you're looking for here
Thanks,
Sam
On 10 April 2018 at 11:55, Rahul Singh wrote:
> That seems to be more of a network segmentation issue. Protect the other
> nodes behind a firewall / security group. Each node in the differ
That seems to be more of a network segmentation issue. Protect the other nodes
behind a firewall / security group. Each node in the different DCs would be
able to talk to each other but the user client machine can only access the
traffic only DC
--
Rahul Singh
rahul.si...@anant.us
Anant Corpor
Thanks Jim for your reply,
> ... just in case even he change his contact points he shouldn't be able
execute queries on DC2.
What I mean was we have 2 DC only 1 serving traffic, Let's say an
individual user wants to run a query from cqlsh/Devcenter on DC serving
requests, I want to prevent it.
Pranay,
> Is it possible to restrict users to specific DC in cassandra, let's say an
> user A is connecting to DC1 and executing queries, how to can I restrict that
> user to that particular DC...
This part sounds like a job for a DC-aware load-balancing policy in the driver.
> ... just in ca
Hi all,
Is it possible to restrict users to specific DC in cassandra, let's say an
user A is connecting to DC1 and executing queries, how to can I restrict
that user to that particular DC, just in case even he change his contact
points he shouldn't be able execute queries on DC2.
Is it something
