Re: Cassandra Mutation object decoding

2016-11-22 Thread J. D. Jordan
You may also want to look at the triggers interface. > On Nov 22, 2016, at 7:45 PM, Chris Lohfink wrote: > > There are different kinds of tombstones, a partition tombstone is held in > the MutableDeletionInfo of the PartitionUpdate that you can get from > deletionInfo() method which returns the

Re: Wiki Contributer

2016-11-22 Thread Dave Brosius
If your wiki-name was ThomasBrown, then you are added, if not let me know what it is. On 11/22/2016 06:33 PM, Thomas Brown wrote: Hi, Could I please be added as a Wiki Contributor Thanks

Re: Cassandra Mutation object decoding

2016-11-22 Thread Nate McCall
Have you explored the QueryProcessor interface? That is a legitimate extension point and may be a more suitable layer at which to integrate. On Wed, Nov 23, 2016 at 1:59 PM, Sanal Vasudevan wrote: > Hi Bejamin, > > Nice to hear from you. > > My goal is to reconstruct the CQL operation from the Mu

Re: Cassandra Mutation object decoding

2016-11-22 Thread Chris Lohfink
There are different kinds of tombstones, a partition tombstone is held in the MutableDeletionInfo of the PartitionUpdate that you can get from deletionInfo() method which returns the private deletionInfo field from the holder. There are also row and cell deletions so you have to handle each of thos

Re: Cassandra Mutation object decoding

2016-11-22 Thread Sanal Vasudevan
Hi Bejamin, Nice to hear from you. My goal is to reconstruct the CQL operation from the Mutation object. So that I can trigger the same action on another NoSQL target like MongoDB. Please let me know know if you have ideas? Many thanks. Sanal On Tue, Nov 22, 2016 at 7:28 PM, Benjamin Lerer w

Wiki Contributer

2016-11-22 Thread Thomas Brown
Hi, Could I please be added as a Wiki Contributor Thanks -- *Thomas Brown* *Digital Marketing Associate * m: +61427864972 MANAGED. SUPPORT. CONSULTING.

[GitHub] cassandra issue #85: sasi: AND optimizations

2016-11-22 Thread blerer
Github user blerer commented on the issue: https://github.com/apache/cassandra/pull/85 Thanks. :-) People are usually tracking the JIRA tickets and not the pull requests. So it is best to keep it in sync with your developments. --- If your project is set up for it, you can reply

[GitHub] cassandra issue #85: sasi: AND optimizations

2016-11-22 Thread iksaif
Github user iksaif commented on the issue: https://github.com/apache/cassandra/pull/85 Done, I'm not yet very familiar with the workflow. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] cassandra issue #85: sasi: AND optimizations

2016-11-22 Thread blerer
Github user blerer commented on the issue: https://github.com/apache/cassandra/pull/85 I guess it is CASSANDRA-12915. Could you mark it as patch available? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project d

[GitHub] cassandra issue #85: sasi: AND optimizations

2016-11-22 Thread blerer
Github user blerer commented on the issue: https://github.com/apache/cassandra/pull/85 Is there a JIRA ticket associated to your patch? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this fe

[GitHub] cassandra pull request #85: sasi: AND optimizations

2016-11-22 Thread iksaif
GitHub user iksaif opened a pull request: https://github.com/apache/cassandra/pull/85 sasi: AND optimizations when op is AND: - do not use indexes that return way more results that the others - do not use more indexes if one of them returns no results - try to use somethi

Re: Cassandra Mutation object decoding

2016-11-22 Thread Benjamin Lerer
Hi Sanal, What you want to do is not an easy stuff and it might break with new major releases. My question would be: why do you want to do that? There might be another way to reach the same goal. Benjamin On Mon, Nov 21, 2016 at 7:14 PM, Sanal Vasudevan wrote: > Thank you Vladimir. > Anyone e