CqlOutputFormat with auth

Hadoop2.6,cassandra2.1.6. Here is the exception stack: Error: java.lang.RuntimeException: InvalidRequestException(why:You have not logged in) at org.apache.cassandra.hadoop.cql3.CqlRecordWriter.(CqlRecordWriter.java:121) at org.apache.cassandra.hadoop.cql3.CqlRecordWriter.(CqlRecordWriter.java:88

timestamp as clustering key doesn't work as expected

Hi, I use a timestamp column as the last clustering key so that I can run query like "timestamp > ... AND timestamp < ...". But it doesn't work as expected. Here is a simplified example. My table: CREATE TABLE test ( tag text, group int, timestamp timestamp, value double, PRIM

Re: timestamp as clustering key doesn't work as expected

What version of Cassandra? I can’t think of a reason why you’d see this output. If you can reliably reproduce, this should be filed as a JIRA. https://issues.apache.org/jira > On Oct 23, 2015, at 8:55 AM, Kai Wang wrote: > > Hi, > > I use a timestamp column as the last clustering key so t

Re: timestamp as clustering key doesn't work as expected

Jon, It's 2.1.10. I will see if I can reproduce it with a simple script. Thanks. On Fri, Oct 23, 2015 at 1:05 PM, Jon Haddad wrote: > What version of Cassandra? I can’t think of a reason why you’d see this > output. If you can reliably reproduce, this should be filed as a JIRA. > https://iss

Re: timestamp as clustering key doesn't work as expected

https://issues.apache.org/jira/browse/CASSANDRA-10583 On Fri, Oct 23, 2015 at 1:26 PM, Kai Wang wrote: > Jon, > > It's 2.1.10. I will see if I can reproduce it with a simple script. > > Thanks. > > On Fri, Oct 23, 2015 at 1:05 PM, Jon Haddad wrote: > >> What version of Cassandra? I can’t think

Re: Is replication possible with already existing data?

Any ideas, please? To repeat, we are using the exact same cassandra-version on all 4 nodes (2.1.10). On Fri, Oct 23, 2015 at 9:43 AM, Ajay Garg wrote: > Hi Michael. > > Please find below the contents of cassandra.yaml for CAS11 (the files on > the rest of the three nodes are also exactly the sam

Re: Automatic pagination does not get all results

Hello Jeff, I'm using Cassandra v2.1.4 I'm expecting the amount of results to be the same every time I use the COPY command (specifically I'm using `COPY TO stdout`). However here are the counts of rows exported each time I ran COPY: 1) 180389 rows exported 2) 181212 rows exported 3) 178641 rows

Re: Is replication possible with already existing data?

Hi Ajay, Please take a look at the cassandra.yaml configuration reference regarding intial_token and num_tokens: http://docs.datastax.com/en/cassandra/2.1/cassandra/configuration/configCassandra_yaml_r.html?scroll=reference_ds_qfg_n1r_1k__initial_token This is basically what Michael was referrin

Re: Is replication possible with already existing data?

Thanks Steve and Michael. Simply uncommenting "initial_token" did the trick !!! Right now, I was evaluating replication, for the case when everything is a clean install. Will now try my hands on integrating/starting replication, with pre-existing data. Once again, thanks a ton for all the help

Some questions about setting public/private IP-Addresses in Cassandra Cluster

Hi All. We have a scenario, where the Application-Server (APP), Node-1 (CAS11), and Node-2 (CAS12) are hosted in DC1. Node-3 (CAS21) and Node-4 (CAS22) are in DC2. The intention is that we provide 4-way redundancy to APP, by specifying CAS11, CAS12, CAS21 and CAS22 as the addresses via Java-Cassa

Downtime-Limit for a node in Network-Topology-Replication-Cluster?

If a node in the cluster goes down and comes up, the data gets synced up on this downed node. Is there a limit on the interval for which the node can remain down? Or the data will be synced up even if the node remains down for weeks/months/years? -- Regards, Ajay