*UPDATE* - I created schema for all the tables in one of the keypsaces,
copied data to new directories and ran nodetool refresh. However, a lot of
data seems to be missing.
I ran nodetool repair on all three nodes one by one. First two nodes took
around 20 minutes (each) to complete. Third node to
*nodetool ring* will give you the tokens for each node on the ring. Each
node has the token range between the previous node's token and its token -
so the token range for each node is the interval (previous_token,
this_token]. The first node in the ring has the range between the last
node's token a
Hi Jacques,
Thanks for bringing this up. I took a quick look through the INFRA project
and saw a couple of resolved issues that might help:
https://issues.apache.org/jira/browse/INFRA-6584?jql=project%20%3D%20INFRA%20AND%20text%20~%20%22mail%20server%20whitelist%22
If those don't do it for you, pl
partition key query,my question
is that is there a convenient way to query a range result or other design for
this requirement,for example 3 or 6 months backward from nowadays,currently we
can only use:
Select * from test where vin =“ZD41578123DSAFWE12313” and create_date in
(20180416, 20180415
Hi Revanth,
I took a quick look and don't think you can override existing mappings. You
should see a warning like this -
18/04/15 19:50:27 WARN CodecRegistry: Ignoring codec CustomTSTypeCodec [date
<-> java.lang.Long] because it collides with previously registered codec
CustomTSTypeCodec [date <
