So that means more than one nodes can be selected to fulfill a range query
based on the token, correct?
I was looking at this link:
https://www.datastax.com/dev/blog/a-deep-look-to-the-cql-where-clause
In the example query,
SELECT * FROM numberOfRequests
WHERE token(cluster, date) > token('
Here's a deck of some proposed additions, discussed at one of the NGCC
sessions last fall:
https://github.com/ngcc/ngcc2017/blob/master/CassandraDataIngestion.pdf
On Tue, Jan 30, 2018 at 5:10 PM, Andrew Prudhomme wrote:
> Hi all,
>
> We are currently designing a system that allows our Cassand
Hi all,
We are currently designing a system that allows our Cassandra clusters to
produce a stream of data updates. Naturally, we have been evaluating if CDC
can aid in this endeavor. We have found several challenges in using CDC for
this purpose.
CDC provides only the mutation as opposed to the
Hi all,
We are currently designing a system that allows our Cassandra clusters to
produce a stream of data updates. Naturally, we have been evaluating if CDC
can aid in this endeavor. We have found several challenges in using CDC for
this purpose.
CDC provides only the mutation as opposed to the
On 01/30/2018 04:03 PM, Michael Shuler wrote:
>
> You could do this in your fork on the trunk repository, but it's
You could do this in your fork on the trunk *branch*, but...
- apologies for mixing terms, while trying to be clear and helpful about
terminology :)
--
Michael
--
On 01/30/2018 03:47 PM, Tyagi, Preetika wrote:
> Hi all,
>
> I'm working on the JIRA ticket CASSANDRA-13981 and pushed a patch
> yesterday, however, I have been suggested to create a branch in my
> github account and then push all changes into that. The patch is too
> big hence this seems to be a
Hi all,
I'm working on the JIRA ticket CASSANDRA-13981 and pushed a patch yesterday,
however, I have been suggested to create a branch in my github account and then
push all changes into that. The patch is too big hence this seems to be a
better approach.
I haven't done it before so wanted to e
A range query can be performed on the token of a partition key, not on the
value.
-Jeremiah
> On Jan 30, 2018, at 12:21 PM, Tyagi, Preetika
> wrote:
>
> Hi All,
>
> I have a quick question on Cassandra's behavior in case of partition keys. I
> know that range queries are allowed in general,
Hi All,
I have a quick question on Cassandra's behavior in case of partition keys. I
know that range queries are allowed in general, however, is it also allowed on
partition keys as well? The partition key is used as an input to determine a
node in a cluster, so I'm wondering how one can possib
Hi dev team,
Can one of you guys take a look on this jira ticket?
https://issues.apache.org/jira/browse/CASSANDRA-14183
It has an a patch available for a known security issue with one of the
dependencies. It has only with trivial code changes. It should be
straightforward to review it. Any feedba
10 matches
Mail list logo