seems a doc error

In ths doc :Enabling JMX authentication In the chapter ： $ nodetool status -u cassandra -pw cassandra should change to $ nodetool -u cassandra -pw cassandra status -

Re: Support for ad-hoc query

Knowing your queries in advance is a hard-core requirement for effective deployment of Cassandra. Ad hoc queries are a very clear anti-pattern for Cassandra. DSE Search does provide support for advanced, complex, and ad hoc queries. Stratio and TupleJump Stargate can also be used. Back to the ques

Re: Support for ad-hoc query

I'll second Jack's detailed response and add that you really should do some discovery to figure out what kinds of queries you may need to support. It might not be possible and often that is the case, but it's worth while to ask the end users what kind of reports they need to run. Allowing arbitrar

Cassandra at Apache: Big Data, Sept 28-30 in Budapest

Hi everybody! Apache is splitting up ApacheCon into two conferences. One will focus on Big Data technologies, the other will focus on everything else. Apache: Big Data will be Sept 28-30 in Budapest, Hungary. The timing is a bit unfortunate, as it is the week following the Cassandra Summit in the

RE: Deserialize the collection type data from the SSTable file

Thanks, Daniel. I didn't realize that Cassandra will serialize one more way using List> for collection types. Reading your example code, I make it work. >From link you gave me, using my test data, I found out one issue though. In >any one row, if the collection column is NULL, I think the logic

Cassandra 2.2, 3.0, and beyond

*As you know, we've split our post-2.1 release into two pieces, with 2.2 to be released in July (rc1 out Monday ) and 3.0 in September.2.2 will include Windows support, commitlog compression , JSON support

Lucene index plugin for Apache Cassandra

Hi all, With the release of Cassandra 2.1.6, Stratio is glad to present its open source Lucene-based implementation of C* secondary indexes as a plugin that can be attached to Apache Cassandra. Before the above changes, Lucene index was distribut

Re: Deserialize the collection type data from the SSTable file

Hi Yong, Glad the code was helpful. I believe it serializes using List> for maps so that it can store the Key of the map as well. Thanks for pointing out the edge case! Thanks, Daniel On Wed, Jun 10, 2015 at 6:39 AM, java8964 wrote: > Thanks, Daniel. > > I didn't realize that Cassandra will s

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

Hi, When executing a DELETE statement with an IN clause, where the list contains partition keys, what is the underlying behaviour with regards to atomicity? DELETE FROM MastersOfTheUniverse WHERE mastersID IN ('Man-At-Arms', 'Teela'); Is it going to act like an atomic batch where if one fails, all

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

Batches don't work like that. It's possible for some to succeed, and later, the rest will. Atomic is the incorrect word to use, it's more like "eventually they will all go through". Do not use IN(), use a whole bunch of prepared statements asynchronously. On Wed, Jun 10, 2015 at 9:26 AM Sotirio

sstable2json references to nonexistent keyspace

I'm trying to use sstable2json in 2.1.6 installation. Note that I'm using the tool from the tarball since the Ubuntu package does not include it. I'm seeing the following error message: ./sstable2json /var/lib/cassandra/data/audits/audits_by_user/audits-audits_by_user-ka-38156-Data.db Filename /v

RE: C* 2.0.15 - java.lang.NegativeArraySizeException

Right. I have had very few problems running mixed versions for normal operations (as long as the versions are “close”). During upgrades, I turn off repairs. Adding/replacing nodes is very infrequent for me, so not much of a consideration. We upgrade as quickly as we can, however, to protect agai

Re: Hundreds of sstables after every Repair

NTP output attached. Any other comments on the two queries ? Thanks Anuj Wadehra Sent from Yahoo Mail on Android From:"Anuj Wadehra" Date:Tue, 9 Jun, 2015 at 10:59 pm Subject:Re: Hundreds of sstables after every Repair Yes. We use NTP. We also thought that drift is creating problems. Our NTP

Re: Hundreds of sstables after every Repair

NTP output attached. Any other comments on the two queries ? Thanks Anuj Wadehra Sent from Yahoo Mail on Android From:"Anuj Wadehra" Date:Tue, 9 Jun, 2015 at 10:59 pm Subject:Re: Hundreds of sstables after every Repair Yes. We use NTP. We also thought that drift is creating problems. Our NTP

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 stateme

Re: Hundreds of sstables after every Repair

Perhaps doing a sstable2json on some of the small tables would shed some illumination. I was going to suggest the anticompaction feature of C*2.1 (which I'm not familiar with), but you're on 2.0. On Tue, Jun 9, 2015 at 11:11 AM, Anuj Wadehra wrote: > We were facing dropped mutations earlier and

RE: Cassandra 2.2, 3.0, and beyond

With 3.0, what happens to existing Thrift-based tables (with dynamic column names, etc.)? Sean Durity From: Jonathan Ellis [mailto:jbel...@gmail.com] Sent: Wednesday, June 10, 2015 10:30 AM To: user Subject: Cassandra 2.2, 3.0, and beyond As you know, we've split our post-2.1 release into two

Re: seems a doc error

Email such doc corrections to : "docs AT datastax dot com" =Rob On Wed, Jun 10, 2015 at 12:57 AM, 曹志富 wrote: > In ths doc :Enabling JMX authentication > > > In the chapter ： > > $ nodetool status -u ca

Re: Cassandra 2.2, 3.0, and beyond

On Wed, Jun 10, 2015 at 1:43 PM, wrote: > With 3.0, what happens to existing Thrift-based tables (with dynamic > column names, etc.)? Just like in Cassandra 2.x, they will show up as COMPACT STORAGE tables in a format that CQL can work with. We're making a few adjustments to how the schema is

Files not removed after compaction

Compaction finished yesterday, but I still have this going on: Space used (live), bytes: 878681716067 Space used (total), bytes: 2227857083852 jbf@ip-10-0-2-98:/ebs/cassandra/data/trends/trends$ sudo lsof *-Data.db COMMAND PID USER FD TYPE DEVICE S

Re: Files not removed after compaction

On Wed, Jun 10, 2015 at 4:15 PM, Jeff Ferland wrote: > Compaction finished yesterday, but I still have this going on: > 1) What version? 2) Probably file a JIRA, esp. if you can repro on another node? 3) if you do 2, reply to thread so we can track! =Rob

Re: Files not removed after compaction

Cassandra 2.0.12-200 / DSE 4.6.1 https://issues.apache.org/jira/browse/CASSANDRA-9577 -Jeff > On Jun 10, 2015, at 4:36 PM, Robert Coli wrote: > > On Wed, Jun 10, 2015 at 4:15 PM, Jeff Ferland > wrote: > Compa

Re: Hundreds of sstables after every Repair

NTP output attached. Any other comments on the two queries ? Thanks Anuj Wadehra Sent from Yahoo Mail on Android From:"Anuj Wadehra" Date:Tue, 9 Jun, 2015 at 10:59 pm Subject:Re: Hundreds of sstables after every Repair Yes. We use NTP. We also thought that drift is creating problems. Our NTP