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 <bhu1ra...@gmail.com> wrote:

> Can it be possible with change log feature implemented in CASSANDRA-8844
> <https://issues.apache.org/jira/browse/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 on parent DC which is taking care of transactional workload?
> On Sun, Sep 18, 2016 at 9:30 PM, Dorian Hoxha <dorian.ho...@gmail.com>
> wrote:
>> Only way I know is in elassandra <https://github.com/vroyer/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 <bhu1ra...@gmail.com>
>> wrote:
>>> 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
>>> replica db's, this helps the parent database to be lightweight and free
>>> from building secondary index on every write.
>>> For analytics & auditing purposes it is essential to serve different
>>> access patterns than that modeled from a partition key fetch perspective,
>>> although a limited reads are needed by users but if enabled cluster wide it
>>> will require index write for every row written on that table on every
>>> single node on every DC even the one which may be serving read operations.
>>> What could be the potential means to solve this problem inside of
>>> cassandra (Not having to ship off the data into elasticsearch etc).
>>> Best Regards,
>>> Bhuvan

Reply via email to