Re: Having secondary indices limited to analytics dc

Hi, Sratio's Lucene index takes a walk around to offer this feature. The index can be created with a configuration option specifying a list of data centers to be excluded from indexing. The index i

Re: Having secondary indices limited to analytics dc

Created CASSANDRA-12663 pls feel free to make edits. From a birds eye view it seems a bit ineffecient to keep doing computations and generating data which may not be put to use. (A user may never read via Secondary Indices on primary transacti

Re: Having secondary indices limited to analytics dc

I don't see why having per DC indexes would be an issue, from a technical standpoint. I suggest putting in a JIRA for it, it's a good idea (if it doesn't exist already). Post back to the ML with the issue #. On Sun, Sep 18, 2016 at 12:26 PM Bhuvan Rawal wrote: > Can it be possible with change

Re: Having secondary indices limited to analytics dc

Can it be possible with change log feature implemented in CASSANDRA-8844 ? i.e. to have two clusters (With different schema definitions for secondary indices) and segregating analytics workload on the other cluster with CDC log shipper enabled

Re: Having secondary indices limited to analytics dc

Only way I know is in elassandra . You spin nodes in dc1 as elassandra (having data + indexes) and in dc2 as cassandra (having only data). On Sun, Sep 18, 2016 at 5:43 PM, Bhuvan Rawal wrote: > Hi, > > Is it possible to have secondary indices (SASI or native

Having secondary indices limited to analytics dc

Hi, Is it possible to have secondary indices (SASI or native ones) defined on a table restricted to a particular DC? For instance it is very much possible in mysql to have a parent server on which writes are being done without any indices (other than the required ones), and to have indices on repl