[GitHub] cassandra-dtest issue #2: Added test to verify indexes are not rebuilt at st...
Github user adelapena commented on the issue: https://github.com/apache/cassandra-dtest/pull/2 +1 --- 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 feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
[GitHub] cassandra-dtest pull request #2: Added test to verify indexes are not rebuil...
Github user asfgit closed the pull request at: https://github.com/apache/cassandra-dtest/pull/2 --- 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 feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Customize Cassandra to execute a query multiple times
Hello all, Is there a way to customize Cassandra to execute a query multiple times? My use case is the following. When the Cassandra server receives queries from remote clients, besides executing those queries, the server also stores the queries. In the future, the server can re-execute stored queries under certain circumstances. Currently, when I re-execute a query, I create an internal QueryState object using: qstate = QueryState forInternalCalls(), and then calls the request.execute(qstate, queryStartNanoTime); However, the execution seems to have no effect on the database. There is also no exception message. Does anyone have a clue on this? Great thanks! Best, Ke
Re: Customize Cassandra to execute a query multiple times
On 2017-07-26 22:19 (-0700), Ke Wang wrote: > Hello all, > > Is there a way to customize Cassandra to execute a query multiple times? > There's always a way... > My use case is the following. When the Cassandra server receives queries > from remote clients, besides executing those queries, the server also > stores the queries. In the future, the server can re-execute stored queries > under certain circumstances. > Seems like an unusual request. Where are you storing the queries? Are these reads or writes? For writes you could just serialize the resulting partitionupdate/mutation into a table a la pre-3.0 hints, and then re-play as needed (though tbh I don't really get the use case)? - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: Customize Cassandra to execute a query multiple times
Hi Jeff, Thanks for the prompt reply. I'm sorry I wasn't clear about my use case. Let's say I just want the server to execute writes that are not directly generated from clients. It can be previously stored queries (the case in my last email), or it can be arbitrarily made-up write requests by the server itself. Can you describe a little bit more on how to implement serializing the mutation into the table? Best, Ke 2017-07-26 22:57 GMT-07:00 Jeff Jirsa : > > > On 2017-07-26 22:19 (-0700), Ke Wang wrote: > > Hello all, > > > > Is there a way to customize Cassandra to execute a query multiple times? > > > > There's always a way... > > > My use case is the following. When the Cassandra server receives queries > > from remote clients, besides executing those queries, the server also > > stores the queries. In the future, the server can re-execute stored > queries > > under certain circumstances. > > > > Seems like an unusual request. Where are you storing the queries? Are > these reads or writes? For writes you could just serialize the resulting > partitionupdate/mutation into a table a la pre-3.0 hints, and then re-play > as needed (though tbh I don't really get the use case)? > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > >
