cql

问题 I'm running Cassandra cluster Software version: 2.0.9 Nodes: 3 Replication factor: 2 I'm having a very simple table where I insert and update data. CREATE TABLE link_list ( url text, visited boolean, PRIMARY KEY ((url)) ); There is no expire on rows and I'm not doing any DELETEs. As soon as I run my application it quickly slows down due to the increasing number of tombstoned cells: Read 3 live and 535 tombstoned cells It gets up to thousands in few minutes. My question is what is responsible

问题 I am using java driver version: 2.1.4 Cassandra version: dsc-cassandra-2.1.10 Output from cql gives the following cqlsh 5.0.1 | Cassandra 2.1.10 | CQL spec 3.2.1 | Native protocol v3 I am protocol V3. But it throws an exception when I try to set it to more than 128 requests per connection. This seems to be a restriction in V2. Explained below: The following code block: PoolingOptions poolingOptions = new PoolingOptions(); poolingOptions.setCoreConnectionsPerHost(HostDistance.LOCAL, 8);

问题 I am using java driver version: 2.1.4 Cassandra version: dsc-cassandra-2.1.10 Output from cql gives the following cqlsh 5.0.1 | Cassandra 2.1.10 | CQL spec 3.2.1 | Native protocol v3 I am protocol V3. But it throws an exception when I try to set it to more than 128 requests per connection. This seems to be a restriction in V2. Explained below: The following code block: PoolingOptions poolingOptions = new PoolingOptions(); poolingOptions.setCoreConnectionsPerHost(HostDistance.LOCAL, 8);

问题 I am using java driver version: 2.1.4 Cassandra version: dsc-cassandra-2.1.10 Output from cql gives the following cqlsh 5.0.1 | Cassandra 2.1.10 | CQL spec 3.2.1 | Native protocol v3 I am protocol V3. But it throws an exception when I try to set it to more than 128 requests per connection. This seems to be a restriction in V2. Explained below: The following code block: PoolingOptions poolingOptions = new PoolingOptions(); poolingOptions.setCoreConnectionsPerHost(HostDistance.LOCAL, 8);

问题 I have a json msg coming from iotHub like: { "deviceId": "abc", "topic": "data", "data": { "varname1": [{ "t": "timestamp1", "v": "value1", "f": "respondFrame1" }, { "t": "timestamp2", "v": "value2", "f": "respondFrame2" }], "varname2": [{ "t": "timestamp1", "v": "value1", "f": "respondFrame1" }, { "t": "timestamp2", "v": "value2", "f": "respondFrame2" }] } } and want to store this by azure stream analytics job into a transact sql like this: ID | deviceId | varname | timestamp | respondFrame

问题 I have a json msg coming from iotHub like: { "deviceId": "abc", "topic": "data", "data": { "varname1": [{ "t": "timestamp1", "v": "value1", "f": "respondFrame1" }, { "t": "timestamp2", "v": "value2", "f": "respondFrame2" }], "varname2": [{ "t": "timestamp1", "v": "value1", "f": "respondFrame1" }, { "t": "timestamp2", "v": "value2", "f": "respondFrame2" }] } } and want to store this by azure stream analytics job into a transact sql like this: ID | deviceId | varname | timestamp | respondFrame

问题 I want to create a table with wide partitions (or, put another way, a table which has no value columns (non primary key columns)) that enables the number of rows in any of its partitions to be efficiently procured. Here is a simple definition of such a table CREATE TABLE IF NOT EXISTS test_table ( partitionKeyCol timestamp clusteringCol timeuuid partitionRowCountCol counter static PRIMARY KEY (partitionKeyCol, clusteringCol) ) The problem with this definition, and others structured like it,

问题 I want to create a table with wide partitions (or, put another way, a table which has no value columns (non primary key columns)) that enables the number of rows in any of its partitions to be efficiently procured. Here is a simple definition of such a table CREATE TABLE IF NOT EXISTS test_table ( partitionKeyCol timestamp clusteringCol timeuuid partitionRowCountCol counter static PRIMARY KEY (partitionKeyCol, clusteringCol) ) The problem with this definition, and others structured like it,

问题 When running the following CQL query: SELECT DISTINCT partition_key FROM table_name; This is supposedly meant to return the list of partition keys that are in use for the given table. However, with the default timeout settings of 10s, it always times out: ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting for replica nodes' responses] message="Operation timed out - received only 0 responses." info={'received_responses': 0, 'required_responses': 1, 'consistency':

问题 When running the following CQL query: SELECT DISTINCT partition_key FROM table_name; This is supposedly meant to return the list of partition keys that are in use for the given table. However, with the default timeout settings of 10s, it always times out: ReadTimeout: Error from server: code=1200 [Coordinator node timed out waiting for replica nodes' responses] message="Operation timed out - received only 0 responses." info={'received_responses': 0, 'required_responses': 1, 'consistency':