Timestamp Query

Hello, How do I set a timestamp value with specific timezone in cassandra. I understand that it captures the timezone of the co ordinator node while inserting. What about if I want to insert and display the timezone that I preferred nstead of the default co ordinator timezone.  Thanks &

Cassandra 3.1 - Aggregation query failure

p of uniquecarrier to tuple<int,int>. The first int in the tuple represents delayed flights of the corresponding uniquecarrier. The second int represents total flights of the uniquecarrier. This aggregation query on a subset of the days of the month works: cqlsh:flightdata> select

Re: Cassandra 3.1 - Aggregation query failure

the partition key in the query ("select late_flights(uniquecarrier, depdel15) from flightsbydate;") Cassandra will perform a full table scan and fetch all the data in memory to apply the aggregate function. With a small Java HEAP size, there is a possibility that Cassandra runs out

Re: Cassandra 3.1 - Aggregation query failure

On Fri, Dec 18, 2015 at 9:17 AM, DuyHai Doan wrote: > Cassandra will perform a full table scan and fetch all the data in memory > to apply the aggregate function. Just to clarify for others on the list: when executing aggregation functions, Cassandra *will* use paging

Query Consistency Issues...

We are encountering a situation in our environment (a 6-node Cassandra ring) where we are trying to insert a row and then immediately update it, using LOCAL_QUORUM consistency (replication factor = 3). I have replicated the issue using the following code:

Re: Query Consistency Issues...

What cassandra and driver versions are you running? It may be that the second update is getting the same timestamp as the first, or even a lower timestamp if it's being processed by another server with unsynced clock, so that update may be getting lost. If you have high frequency updates in the

Re: Query Consistency Issues...

On Tue, Dec 15, 2015 at 2:57 PM Paulo Motta wrote: > What cassandra and driver versions are you running? > > We are using 2.1.7.1 > It may be that the second update is getting the same timestamp as the > first, or even a lower timestamp if it's being processed by

Re: Query Consistency Issues...

I agree with Jon. It's almost a statistical certainty that such updates will be processed out of order some of the time because the clock sync between machines will never be perfect. Depending on how your actual code that shows this problem is structured, there are ways to reduce or eliminate

Re: Query Consistency Issues...

High volume updates to a single key in a distributed system that relies on a timestamp for conflict resolution is not a particularly great idea. If you ever do this from multiple clients you'll find unexpected results at least some of the time. On Tue, Dec 15, 2015 at 12:41 PM Paulo Motta

RE: No query results while expecting results

nt_id 5 From: Carlos Alonso [mailto:i...@mrcalonso.com] Sent: Monday, November 23, 2015 9:00 PM To: user@cassandra.apache.org Subject: Re: No query results while expecting results Did you tried to observe it using cassandra-cli? (the thrift client) It shows the 'disk-layout' of the data and may he

Re: No query results while expecting results

= cluster.connect(KEYSPACE); try { session.execute("INSERT INTO " + TABLENAME + "(tnt_id, data) VALUES (5, 'cql test value')"); } finally { session.close(); } } finally { cluster.close();

RE: No query results while expecting results

It might be a consistency issue. Assume your data for tnt 5 should be on nodes 1 and 2, but actually never got to node 1 for various reasons, and the hint wasn’t replayed for some reason and you didn’t run repairs. The data for tnt 5 is only on node 2. A query without restrictions

Re: No query results while expecting results

> 0 | {"v":1451221,"s":2130304,"r":104769,"u":"http://www.example.com"} > 62015061055 | 2147429759 | 35b97470-0f68-11e5-8cc3-000c2981ebb4 | > 1 | > {"v":1453821,"s":2134354,"r":105462,"q"

No query results while expecting results

ebb4 |0 | {"v":1451221,"s":2130304,"r":104769,"u":"http://www.example.com"} 62015061055 | 2147429759 | 35b97470-0f68-11e5-8cc3-000c2981ebb4 | 1 | {"v":1453821,"s":2134354,"r":105462,"q":"13082ede-

Re: No query results while expecting results

Can you run the trace again for the query "select * " without any conditions and see if you are getting results for tnt_id=5? On Mon, Nov 23, 2015 at 1:23 PM, Ramon Rockx <ra...@iqnomy.com> wrote: > Hello Oded and Carlos, > > Many thanks for your tips. I modified the c

Re: No query results while expecting results

14:13:05,898 | 192.168.0.210 |276 Executing single-partition query on te | 14:13:05,898 | 192.168.0.211 |259 Enqueuing data request to / 192.168.0.211 | 14:13:05,898 | 192.168.0.210 |

Re: No query results while expecting results

Hello Prem, On Mon, Nov 23, 2015 at 2:36 PM, Prem Yadav <ipremya...@gmail.com> wrote: > Can you run the trace again for the query "select * " without any > conditions and see if you are getting results for tnt_id=5? > <http://www.iqnomy.com/> Of course, h

Re: No query results while expecting results

On 23 November 2015 at 13:55, Ramon Rockx <ra...@iqnomy.com> wrote: > Hello Prem, > > On Mon, Nov 23, 2015 at 2:36 PM, Prem Yadav <ipremya...@gmail.com> wrote: > >> Can you run the trace again for the query "select * " without any >> conditions and s

Re: No query results while expecting results

com> wrote: > >> Hello Prem, >> >> On Mon, Nov 23, 2015 at 2:36 PM, Prem Yadav <ipremya...@gmail.com> wrote: >> >>> Can you run the trace again for the query "select * " without any >>> conditions and see if you are getting results for t

Re: No query results while expecting results

Hello Carlos, On Mon, Nov 23, 2015 at 3:31 PM, Carlos Alonso wrote: > Well, this makes me wonder how varints are compared in java vs python > because the problem may be there. > > I'd suggest getting the token, to know which server contains the missing > data. Go there and

Re: No query results while expecting results

Did you tried to observe it using cassandra-cli? (the thrift client) It shows the 'disk-layout' of the data and may help as well. Otherwise, if you can reproduce it having a varint as the last part of the partition key (or at any other location), this may well be a bug. Carlos Alonso | Software

Re: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

Michael, Thanks for pointing that out. It is a driver issue affecting CQL export (but not the execution API). I created a ticket to track and resolve: https://datastax-oss.atlassian.net/browse/PYTHON-447 Adam On Sat, Nov 21, 2015 at 8:38 AM, Laing, Michael wrote: >

Re: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

> > All these pain we need to take because the column names have special >> character like " ' _- ( ) '' ¬ " etc. >> > Hmm. I tried: cqlsh:test> create table quoted_col_name ( pk int primary key, "'_-()""¬" int); cqlsh:test> select * from quoted_col_name; *pk* | *'_-()"¬* +- (0

Re: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

Quickly reviewing this spec: https://github.com/apache/cassandra/blob/trunk/doc/native_protocol_v4.spec I see that column_name is a utf-8 encoded string. So you should be able to pass unicode into the python driver and have it do the "right thing". If not, it's a bug IMHO. On Sat, Nov 21, 2015

RE: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

if these column_name(s) exist in the table 4) If the column don't exist in the table "ALTER table tablename add new column_name text" 5) Inject data into this new column "Update table name set column_name =value where id=blah" We did tried the map columns, but the query pa

Re: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

new column names from > this XML > 3) check the system.schema_columns if these column_name(s) exist in the > table > 4) If the column don't exist in the table "ALTER table tablename add new > column_name text" > 5) Inject data into this new column "Update table name set column_

UDT - Collection - Query

:'applicable-security-policy',value: {'FOX'}}); *Can I query Something likecqlsh:mykeyspace> SELECT * FROM test_path3 where mdata.value CONTAINS {'Mime'};SyntaxException: * Thanks regards Neha

Re: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

t; ALTER TABLE test.iau ADD col8 text > ALTER TABLE test.iau ADD col9 text > E > == > > -- > Traceback (most recent call last): > File "U

RE: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

2015 11:55 To: user@cassandra.apache.org Subject: Re: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement Maybe schema disagreement? Run nodetool describecluster to discover Carlos Alonso | Software Engineer | @calonso<https://twitter.com/calo

RE: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

you know which one? From: Laing, Michael [michael.la...@nytimes.com] Sent: 13 November 2015 12:26 To: user@cassandra.apache.org Subject: Re: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement Dynamic schema changes

Re: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

ed to be updated for some parameter in > cassandra.yaml > > Do you know which one? > > > > -- > *From:* Laing, Michael [michael.la...@nytimes.com] > *Sent:* 13 November 2015 12:26 > > *To:* user@cassandra.apache.org > *Subject:* Re: G

Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

qlAlterStatement1) File "/usr/local/lib/python2.7/site-packages/cassandra/cluster.py", line 1405, in execute result = future.result(timeout) File "/usr/local/lib/python2.7/site-packages/cassandra/cluster.py&qu

Re: Getting code=2200 [Invalid query] message=Invalid column name ... while executing ALTER statement

er@cassandra.apache.org > *Subject:* Re: Getting code=2200 [Invalid query] message=Invalid column > name ... while executing ALTER statement > > Maybe schema disagreement? > > Run nodetool describecluster to discover > > Carlos Alonso | Software Engineer | @calonso <htt

Re: Read query taking a long time

Well... I think that pretty much is showing the problem. The problem I'd say is a bad data model. Your read query is perfect, it hits a single partition and that's the best situation, but on the other hand, it turns out that there are one or two huge partitions and fully reading them is extremely

Re: Read query taking a long time

t; I checked and on all nodes, the read latency and read local latency are > within 15 to 40ms. > > I also noticed that C* was taking a fair bit of CPU on some of the nodes > (ranging from 60% to 200%), looking at ttop output it was mostly taken by > SharedPool-Worker threads, which I assume are the thread that are doing the > real query work. > > Well, I'm puzzled, and I'll keep searching, thanks for your help! > -- > Brice Figureau >

Re: Read query taking a long time

ume are the thread that are doing the real query work. Well, I'm puzzled, and I'll keep searching, thanks for your help! -- Brice Figureau

Re: Read query taking a long time

l, things > are a bit better. > > This might be because I moved from openjdk 7 to oracle jdk 8 after > having seen a warning in the C* log about openjdk, and I also added a > node (for other reasons). > > Now the query itself takes only 1.5s~2s instead of the 5s~6s it was > t

Re: Read query taking a long time

Hi, Thanks for your answer. Unfortunately since I wrote my e-mail, things are a bit better. This might be because I moved from openjdk 7 to oracle jdk 8 after having seen a warning in the C* log about openjdk, and I also added a node (for other reasons). Now the query itself takes only 1.5s~2s

Re: Read query taking a long time

read all I could find on how cassandra works, I'm still wondering why > the following query takes more than 5s to return on a simple (and modest) 3 > nodes cassandra 2.1.9 cluster: > > SELECT sequence_nr, used > FROM messages > WHERE persistence_id = 'session-SW' AND partiti

Re: Read query taking a long time

s Alonso | Software Engineer | @calonso <https://twitter.com/calonso> > > On 17 October 2015 at 16:15, Brice Figureau <brice+cassan...@daysofwonder.com > <mailto:brice+cassan...@daysofwonder.com>> wrote: > Hi, > > I've read all I could find on how cassand

Read query taking a long time

Hi, I've read all I could find on how cassandra works, I'm still wondering why the following query takes more than 5s to return on a simple (and modest) 3 nodes cassandra 2.1.9 cluster: SELECT sequence_nr, used FROM messages WHERE persistence_id = 'session-SW' AND partition_nr = 0

Re: unchecked_tombstone_compaction - query

Hello Deepak, The dev@cassandra list is exclusive for development announcements and discussions, so I will reply to users@cassandra as someone else might have a similar question. Basically, there is pre-check, that defines which sstables are eligible for single-sstable tombstone compaction, and

Re: unchecked_tombstone_compaction - query

On Thu, Oct 15, 2015 at 9:01 AM, Paulo Motta wrote: > (OP says:) So - isn't setting unchecked_tombstone_compaction to "true" a >> dangerous setting? Won't it cause resurrections? What is the use case for >> this knob, and when do I know I can set it to true safely? >>

Re: Cassandra query degradation with high frequency updated tables.

-----++---+ >>> >>> >&g

Re: Cassandra query degradation with high frequency updated tables.

--++---+ Execute CQL3 query | 2015-10-09 15:31:28.70 | 172.31.17.129

Re: Cassandra query degradation with high frequency updated tables.

gt; | >> *timestamp* | *source*| *source_elapsed* >> >> ------++

Re: Cassandra query degradation with high frequency updated tables.

> | timestamp > | source| source_elapsed > --++---+ > >

Re: Cassandra query degradation with high frequency updated tables.

estamp* | *source*| *source_elapsed* > > --++---+---- > > > *Execute CQL3 query* | *2015-10-09 > 15:31:28.70* | *172.31.17.129* | *0* > *Parsing select * from processinfometric_profile where > profilecontext='GEN

Re: Cassandra query degradation with high frequency updated tables.

ain analytics that can use in the > context of the ‘thing’ or in the context of specific thing and subthing. > > A profile can be defined as monthly, daily, hourly. So in case of monthly the > month will be set to the current month (i.e. ‘Oct’) and the day and hour will >

Re: Cassandra query degradation with high frequency updated tables.

ra.yaml to avoid it. If you still see performance problems after that, can you try tracing the query with cqlsh? On Fri, Oct 9, 2015 at 12:01 PM, Nazario Parsacala <dodongj...@gmail.com> wrote: > So I upgraded to 2.2.2 and change the compaction strategy from >

Re: Cassandra query degradation with high frequency updated tables.

;> This profile will then be use for certain analytics that can use in the >> context of the ‘thing’ or in the context of specific thing and subthing. >> >> A profile can be defined as monthly, daily, hourly. So in case of monthly >> the month will be set to the current month

Re: Cassandra query degradation with high frequency updated tables.

t; subthings text, >> lastvalue double, >> count int, >> stddev double, >> PRIMARY KEY ((id, month, day, hour), subthings) >> ) WITH CLUSTERING ORDER BY (subthings ASC) ); >> >> >> This profile will then be use for certai

Re: Cassandra query degradation with high frequency updated tables.

subthing. > > A profile can be defined as monthly, daily, hourly. So in case of monthly > the month will be set to the current month (i.e. ‘Oct’) and the day and > hour will be set to empty ‘’ string. > > > The problem that we have observed is that over time (actuall

Cassandra query degradation with high frequency updated tables.

is that over time (actually in just a matter of hours) we will see a huge degradation of query response for the monthly profile. At the start it will be respinding in 10-100 ms and after a couple of hours it will go to 2000-3000 ms . If you leave it for a couple of days you will start

Cassandra Query using UDF

Hello I am wondering is it possible to execute a search using a Cassandra UDF. Similarly to the way I can execute find queries in mongo using custom javascript. Thanks Michael.

RE: Cassandra Query using UDF

2015 12:35 À : user@cassandra.apache.org Objet : Cassandra Query using UDF Hello I am wondering is it possible to execute a search using a Cassandra UDF. Similarly to the way I can execute find queries in mongo using custom javascript. Thanks Michael. Ce message et les pièces jointes sont

cassandra-stress where query with greater than operator

Hi All. I'm trying to set up cassandra load testing and came up with the next YAML config (https://gist.github.com/folex/d297cc8208a2e54a36d7) : keyspace: stress keyspace_definition: | CREATE KEYSPACE stress WITH replication = {'class': 'SimpleStrategy', 'replication_factor': 3}; table:

Re: SELECT *... query times out on a particular table

...@baseboxsoftware.com wrote: Hello, Any select all or select count query on a particular table is timing out with Cassandra::Errors::TimeoutError: Timed out A “SELECT * FROM table WHERE partition key = ‘partition key value’ on the table works, but a “SELECT * FROM table LIMIT 1; does not work. All other

Re: SELECT *... query times out on a particular table

On Mon, Aug 3, 2015 at 2:48 PM, Sid Tantia sid.tan...@baseboxsoftware.com wrote: Any select all or select count query on a particular table is timing out with Cassandra::Errors::TimeoutError: Timed out A “SELECT * FROM table WHERE partition key = ‘partition key value’ on the table works

Re: SELECT *... query times out on a particular table

Check Cassandra logs for tombstone threshold error On Aug 3, 2015 7:32 PM, Robert Coli rc...@eventbrite.com wrote: On Mon, Aug 3, 2015 at 2:48 PM, Sid Tantia sid.tan...@baseboxsoftware.com wrote: Any select all or select count query on a particular table is timing out with Cassandra::Errors

SELECT *... query times out on a particular table

Hello, Any select all or select count query on a particular table is timing out with Cassandra::Errors::TimeoutError: Timed out A “SELECT * FROM table WHERE partition key = ‘partition key value’ on the table works, but a “SELECT * FROM table LIMIT 1; does not work. All other tables

答复: query statement return empty

Using java/C# rewrite the test case, the results are consistency. Is there any problem for the python driver? 发件人: 鄢来琼 发送时间: Friday, July 31, 2015 9:03 AM 收件人: 'user@cassandra.apache.org' 主题: query statement return empty Hi ALL The result of “select * from t_test where id = 1” statement

Re: query statement return empty

What consistency level are you using with your query? What replication factor are you using on your keyspace? Have you run repair? The most likely explanation is that you wrote with low consistency (ANY, ONE, etc), and that one or more replicas does not have the cell. You’re then reading

query statement return empty

Hi ALL The result of “select * from t_test where id = 1” statement is not consistency, Could you tell me why? test case, I = 0; While I 5: result = cassandra_session.execute(“select ratio from t_test where id = 1”) print result testing result: [Row(ratio=Decimal('0.000'))] []

RE: query statement return empty

@cassandra.apache.org 主题: Re: query statement return empty What consistency level are you using with your query? What replication factor are you using on your keyspace? Have you run repair? The most likely explanation is that you wrote with low consistency (ANY, ONE, etc), and that one or more

cassandra-stress: Not enough replica available for query at consistency LOCAL_ONE (1 required but only 0 alive)

for query at consistency LOCAL_ONE (1 required but only 0 alive) at org.apache.cassandra.stress.Operation.error(Operation.java:216) at org.apache.cassandra.stress.Operation.timeWithRetry(Operation.java:188) at org.apache.cassandra.stress.operations.predefined.CqlOperation.run(CqlOperation.java:99

Re: howto do sql query like in a relational database

...@gmx.de] Sent: Tuesday, July 21, 2015 7:54 PM To: user@cassandra.apache.org Subject: howto do sql query like in a relational database Hi, I have a simple (perhaps stupid) question. If I want to *search* data in cassandra, how could find in a text field all records which start with 'Cas

howto do sql query like in a relational database

Hi, I have a simple (perhaps stupid) question. If I want to *search* data in cassandra, how could find in a text field all records which start with 'Cas' ( in sql I do select * from table where field like 'Cas%') I know that this is not directly possible. - But how is it possible? - Do

RE: howto do sql query like in a relational database

@cassandra.apache.org Subject: howto do sql query like in a relational database Hi, I have a simple (perhaps stupid) question. If I want to *search* data in cassandra, how could find in a text field all records which start with 'Cas' ( in sql I do select * from table where field like 'Cas%') I

How to export query results (milions rows) as CSV fomat?

Hi, Is there any way to export the results of a query (e.g. select * from tbl1 where id =aa and loc =bb) into a file as CSV format? I tried to use COPY command with cqlsh, but the command does not work when you have where condition ?!!! does any have any idea how to do this? best, /Shahab

Re: Atomic behavior and efficiency of a DELETE query with an IN clause

Similarly, should we send multiple SELECT requests or a single one with a SELECT...IN ? On Wednesday, June 10, 2015 11:27 AM, Sotirios Delimanolis sotodel...@yahoo.com wrote: Will this eventually they will all go through behavior apply to the IN? How is this query written

Re: Atomic behavior and efficiency of a DELETE query with an IN clause

...IN ? On Wednesday, June 10, 2015 11:27 AM, Sotirios Delimanolis sotodel...@yahoo.com wrote: Will this eventually they will all go through behavior apply to the IN? How is this query written to the commitlog? Do you mean prepare a query like DELETE FROM MastersOfTheUniverse WHERE mastersID

RE: Support for ad-hoc query

to Hadoop for querying by hive. Example: “We found a few records with incorrect data. How many more records like that are out there?” Sean Durity From: Peter Lin [mailto:wool...@gmail.com] Sent: Wednesday, June 10, 2015 8:17 AM To: user@cassandra.apache.org Subject: Re: Support for ad-hoc query

Re: Support for ad-hoc query

No dispute about that. But the main design requirement Cassandra strives to meet is to be a blazing fast transactional database - here's the key, give me the data, and here's the key, write this data. Any additional query requirements are a distant second at best. A big part of that transactional

Re: Support for ad-hoc query

on the cluster? 3. How complex do you expect them to be - how many clauses and operators? 4. What is their net cardinality - are they selecting just a few rows or many rows? 5. Do they have individual query clauses that select many rows even if the net combination of all select clauses is not so many rows

Re: Support for ad-hoc query

arbitrary ad-hoc queries is a known anti-pattern for cassandra. If the system needs to query multiple cf to derive/calculate some result, using Cassandra alone isn't going to do it. You'll need some other system to give you better query capabilities like Hive. If you need data warehouse like features

Re: Atomic behavior and efficiency of a DELETE query with an IN clause

a single DELETE query and provide all the keys in the IN argument or should I add 3000 DELETE queries to a BATCH statement? Thank you, Sotirios

Atomic behavior and efficiency of a DELETE query with an IN clause

, all fail? If that is the case, is there any reason to use a BATCH statement with multiple single DELETE statement or should we always prefer a DELETE with an IN clause?  For example, given 3000 keys for rows I want to delete, should I issue a single DELETE query and provide all the keys

Re: Atomic behavior and efficiency of a DELETE query with an IN clause

Will this eventually they will all go through behavior apply to the IN? How is this query written to the commitlog? Do you mean prepare a query likeDELETE FROM MastersOfTheUniverse WHERE mastersID = ?;and execute it asynchronously 3000 times or add 3000 of these DELETE (bound) prepared

Re: Support for ad-hoc query

@cassandra.apache.org Subject: Support for ad-hoc query Hi All, I have an web application running with my backend data stored in cassandra. Now I want to do some analysis on the data stored which requires some ad-hoc queries fired on cassandra. How can I do the same? Regards, Seenu.

Support for ad-hoc query

Hi All, I have an web application running with my backend data stored in cassandra. Now I want to do some analysis on the data stored which requires some ad-hoc queries fired on cassandra. How can I do the same? Regards, Seenu.

Re: Support for ad-hoc query

what do you mean by ad-hoc queries? Do you mean simple queries against a single column family aka table? Or do you mean MDX style queries that looks at multiple tables? if it's MDX style queries, many people extract data from Cassandra into a data warehouse that support multi-dimensional cubes.

Re: Support for ad-hoc query

Thanks guys for the inputs. By ad-hoc queries I mean that I don't know the queries during cf design time. The data may be from single cf or multiple cf. (This feature maybe required if I want to do analysis on the data stored in cassandra, do you have any better ideas)? Regards, Seenu. On

Re: Query returning tombstones

Hi Jens, thanks a lot for the link! Your ticket seems very similar to my request. kind regards, Christian On Sat, May 2, 2015 at 2:25 PM, Jens Rantil jens.ran...@tink.se wrote: Hi Christian, I just know Sylvain explicitly stated he wasn't a fan of exposing tombstones here:

query contains IN on the partition key and an ORDER BY

Hi I have run into the following issue https://issues.apache.org/jira/browse/CASSANDRA-6722 when running a query (contains IN on the partition key and an ORDER BY ) using datastax driver for Java. However, I am able to run this query alright in cqlsh. cqlsh: show version; [cqlsh 5.0.1

Re: query contains IN on the partition key and an ORDER BY

/browse/CASSANDRA-6722 when running a query (contains IN on the partition key and an ORDER BY ) using datastax driver for Java. However, I am able to run this query alright in cqlsh. cqlsh: show version; [cqlsh 5.0.1 | Cassandra 2.1.2 | CQL spec 3.2.0 | Native protocol v3] cqlsh:gps select

Re: Query returning tombstones

Hi Christian, I just know Sylvain explicitly stated he wasn't a fan of exposing tombstones here: https://issues.apache.org/jira/browse/CASSANDRA-8574?focusedCommentId=14292063page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14292063 Cheers, Jens On Wed, Apr 29, 2015

Query returning tombstones

Hi, did anybody ever raise a feature request for selecting tombstones in CQL/thrift? It would be nice if I could use CQLSH to see where my tombstones are coming from. This would much more convenient than using sstable2json. Maybe someone can point me to an existing jira-ticket, but I also

Delete query range limitation

I understand that range deletes are currently not supported ( http://stackoverflow.com/questions/19390335/cassandra-cql-delete-using-a-less-than-operator-on-a-secondary-key ) Since Cassandra now does have range tombstones is there a reason why it can't be allowed? Is there a ticket for supporting

Re: log all the query statement

the maxBackupIndex or maxFileSize to make sure u keep enough log files around. anishek On Thu, Apr 2, 2015 at 11:53 AM, 鄢来琼 laiqiong@gtafe.com wrote: Hi all, Cassandra 2.1.2 is used in my project, but some node is down after executing query some statements. Could I configure the Cassandra to log all

log all the query statement

Hi all, Cassandra 2.1.2 is used in my project, but some node is down after executing query some statements. Could I configure the Cassandra to log all the executed statement? Hope the log file can be used to identify the problem. Thanks. Peter

Re: 2d or multi dimension range query in cassandra CQL

:{} } }' }; If I insert data in the table along with points list. The following query won't give any results (0 rows): SELECT * FROM RESULTS1 WHERE stargate ='{ filter: { type: range, field: x, lower: 0 } }'; I tried removing points listdouble from

Re: 2d or multi dimension range query in cassandra CQL

. The following query won't give any results (0 rows): SELECT * FROM RESULTS1 WHERE stargate ='{ filter: { type: range, field: x, lower: 0 } }'; I tried removing points listdouble from the table and it works i.e. same query will return results. Can somebody

Re: 2d or multi dimension range query in cassandra CQL

':'{ fields:{ eyeColor:{}, age:{}, phone:{} } }' }; If I insert data in the table along with points list. The following query won't give any results (0 rows): SELECT * FROM RESULTS1 WHERE stargate

Re: 2d or multi dimension range query in cassandra CQL

of Allow Filtering option. cqlsh:images *select * from results1 where image_caseid='mehak' and x 100 and y 100 order by x allow filtering;* *code=2200 [Invalid query] message=No indexed columns present in by-columns clause with Equal operator* My table definition is : *CREATE TABLE

Re: 2d or multi dimension range query in cassandra CQL

; code=2200 [Invalid query] message=No indexed columns present in by-columns clause with Equal operator My table definition is : CREATE TABLE images.results1 (uuid uuid, analysis_execution_id varchar, analysis_execution_uuid uuid, x double, y double, loc varchar, w double, h double

2d or multi dimension range query in cassandra CQL

* from results1 where image_caseid='mehak' and x 100 and y 100 order by x allow filtering;* *code=2200 [Invalid query] message=No indexed columns present in by-columns clause with Equal operator* My table definition is : *CREATE TABLE images.results1 (uuid uuid, analysis_execution_id varchar

Re: using or in select query in cassandra

Hi Rahul, No, you can't do this in a single query. You will need to execute two separate queries if the requirements are on different columns. However, if you'd like to select multiple rows of with restriction on the same column you can do that using the `IN` construct: select * from table where

Re: using or in select query in cassandra

/cassandra-query-patterns-not-using-the-in-query-for-multiple-partitions/ On Mon, Mar 2, 2015 at 12:36 AM Jens Rantil jens.ran...@tink.se wrote: Hi Rahul, No, you can't do this in a single query. You will need to execute two separate queries if the requirements are on different columns. However

Re: using or in select query in cassandra

I would also like to add that if you avoid IN and use async queries instead, it is pretty trivial to use a semaphore or some other limiting mechanism to put a ceiling on the amount on concurrent work you are sending to the cluster. If you use a query with an IN clause with a thousand things

<    1   2   3   4   5   6   7   8   9   10   >