Re: Does Cassandra supports ACID txn

On Thu, Apr 19, 2018 at 11:13 AM Rajesh Kishore wrote: > Thanks for the response. Let me put my question again wrt a example > > I want to perform a atomic txn say insert/delete/update on a set of tables > TableA > TableB > TableC > > When these are performed as batch operations and let us say so

Re: Cassandra Needs to Grow Up by Version Five!

> > I have to disagree with people here and point out that just creating > JIRA's and (trying to) have discussions about these issues will not lead to > change in any reasonable timeframe, because everyone who could do the work > has an endless list of bigger fish to fry. I strongly encourage you t

Proposal for deprecating/removing the read_repair_chance/dclocal_read_repair_chance table options

We are considering deprecating and them ultimately removing the 2 table options: 'read_repair_chance' and 'dclocal_read_repair_chance'. The rational and much more details are on CASSANDRA-13910 (https://issues.apache.org/jira/browse/CASSANDRA-13910), so I won't repeat it here. The goal of this ema

Re: WriteTimeoutException with LWT after few milliseconds

This is https://issues.apache.org/jira/browse/CASSANDRA-9328 and I'd rather not repeat myself here so I'll let you read the details. Let's maybe not open another JIRA ticket though since we have this one. On Wed, Apr 19, 2017 at 4:29 PM, benjamin roth wrote: > Thanks, Jeff! > > As soon as I have

Re: Count(*) is not working

ion it >> almost always works and others are under the impression it almost never >> works. >> >> On Friday, February 17, 2017, kurt greaves wrote: >> >>> really... well that's good to know. it still almost never works though. >>> i guess every ti

Re: Count(*) is not working

On Fri, Feb 17, 2017 at 11:54 AM, kurt greaves wrote: > if you want a reliable count, you should use spark. performing a count (*) > will inevitably fail unless you make your server read timeouts and > tombstone fail thresholds ridiculous > That's just not true. count(*) is paged internally so w

Re: DELETE/SELECT with multi-column PK and IN

. But as I said, we didn't fix that inconsistency because we're all busy and it's not really that important in practice. The project of course welcome any contributions though :) > > 2017-02-09 10:43 GMT+01:00 Sylvain Lebresne : > >> This is a statement on multiple partiti

Re: DELETE/SELECT with multi-column PK and IN

This is a statement on multiple partitions and there is really no optimization the code internally does on that. In fact, I strongly advise you to not use a batch but rather simply do a for loop client side and send statement individually. That way, your driver will be able to use proper token-awar

Re: Benefit of LOCAL_SERIAL consistency

On Fri, Dec 9, 2016 at 1:35 AM, Edward Capriolo wrote: > > I copied the wrong issue: > > The core issue was this: https://issues.apache. > org/jira/browse/CASSANDRA-6123 > Well, my previous remark applies equally well to this ticket so let me just copy-paste: "That ticket has nothing to do with L

Re: Benefit of LOCAL_SERIAL consistency

> The reason you don't want to use SERIAL in multi-DC clusters I'm not a fan of blanket statements like that. There is a high cost to SERIAL consistency in multi-DC setups, but if you *need* global linearizability, then you have no choice and the latency may be acceptable for your use case. Take t

Re: Why does `now()` produce different times within the same query?

On Thu, Dec 1, 2016 at 4:44 PM, Edward Capriolo wrote: > > I am not sure you saw my reply on thread but I believe everyone's needs > can be met I will copy that here: > I saw it, but the real problem that was raised initially was not that of UDF and of allowing both behavior. It's a matter of pe

Re: Why does `now()` produce different times within the same query?

One can of course always open a JIRA, but I'm going to strongly disagree with a change here (outside of a documentation one that is). The now() function is a timeuuid generator, and it thus generates a unique timeuuid on every call, as specified by the timeuuid spec. I'll note that document lists

Re: Issue with Unexpected exception

>From the trace, "Connection reset by peer" simply mean the client disconnected, which isn't necessary a problem/abnormal per se (and if it is, it sounds more like a client issue than anything else). That said, I'm not sure why 3.0.8 log this at INFO now, as that's not really a problem, so if you c

Re: Question about end of life support for Apache Cassandra 2.1 and 2.2

"unsupported" means there won't be any more release, so no more patches whatsoever and you're on your own. On Thu, Sep 1, 2016 at 12:09 AM, Anmol Sharma wrote: > According to the download page, > Apache Cassandra 2.1 is supported with critical fixes only t

Re: testing retry policy

On Wed, Aug 31, 2016 at 6:56 PM, Jimmy Lin wrote: > hi all, > I have some customized retry policies that want to test. > In my single node local cluster, is there anyway to simulate the > read/write timeout and or unavailable exception? > I tried to kill the Cassandra process but it won't result

[ANNOUNCEMENT] Website update

Wanted to let everyone know that if you go to the Cassandra website (cassandra.apache.org), you'll notice that there has been some change. Outside of a face lift, the main change is a much improved documentation section (http://cassandra.apache.org/doc/). As indicated, that documentation is a work-

Re: Wireshark and CQL

Good stuff, thanks for sharing. On Sun, Jun 5, 2016 at 12:45 PM, Benoît Canet wrote: > > Hi List, > > I am from ScyllaDB and took some time to iterate on the > wireshark CQL dissector that was previously written by > Aaron Ten Clay. > > The result is that wireshark upstream now have a fully work

Re: Proper use of COUNT

> > > Accept for relatively small or narrow queries, it seems to have a > propensity for timing out. > For recent enough version of C*, it shouldn't since it pages internally (it will be slow and as always be, but it shouldn't time out if some decent page size is used, which should be the default)

Re: Clustering key and secondary index behavior changed between 2.0.11 and 3.3.0

I'm surprised this would have fall through the cracks but that certainly look like a regression (a bug). If you can reproduce on 3.0.4 (just to make sure we haven't fixed it recently), then please open a ticket in https://issues.apache.org/jira/browse/CASSANDRA/ with your repro steps. On Tue, Apr

Re: Using User Defined Functions in UPDATE queries

t; looked like an optimal way to avoid having all the clients perform > read-updates patterns and worrying about the clients stepping on each > others data, as well as handling cases where duplicate messages were > received by different receivers. So it’s starting to look like I might > ne

Re: Using User Defined Functions in UPDATE queries

UDF are usable in UPDATE statement as actually trying them shows, it's just the documented grammar that needs fixing. But as far as doing something like: UPDATE test_table SET data=max_int(data,5) WHERE idx='abc’; this is indeed *not* supported and likely never will. One big pillar of C* design

Re: Duplicated key with an IN statement

That behavior has been changed in 2.2 and upwards. If you don't like it, upgrade. In the meantime, it's probably not hard to avoid passing duplicate keys in IN. On Thu, Feb 4, 2016 at 3:48 PM, Edouard COLE wrote: > Hello, > > > > When running that kind of query with TRACING ON; I noticed the coo

Re: Java Driver Question

As a side note, if your email subject is "Java Driver Question", then this almost surely belong to the java driver mailing list. Please try to respect other subscribers by using the most appropriate mailing list when possible. On Tue, Feb 2, 2016 at 5:01 PM, Richard L. Burton III wrote: > Very n

Re: How are timestamps selected for LWTs?

On Tue, Feb 2, 2016 at 10:46 AM, Nicholas Wilson < nicholas.wil...@realvnc.com> wrote: > Hi, > > In the Cassandra docs I've read, it's not described how the timestamp is > determined for LWTs. It's not possible to specify a timestamp with "USING > TIMESTAMP ...", and my best guess is that in the "

Important notice for upgrades from 2.2.X to 3.Y

The native protocol is the name we give to the protocol used between CQL drivers and the server. That protocol is versioned and a new version, version 4, was introduced in Cassandra 2.2.0. We recently uncovered a compatibility bug in that 4th version (https://issues.apache.org/jira/browse/CASSANDRA

Re: [Marketing Mail] Re: [Marketing Mail] can't make any permissions change in 2.2.4

. > > > On Fri, Dec 18, 2015 at 5:05 AM, Reynald Bourtembourg < > reynald.bourtembo...@esrf.fr> wrote: > >> Done: >> https://issues.apache.org/jira/browse/CASSANDRA-10904 >> >> >> >> On 18/12/2015 10:51, Sylvain Lebresne wrote: >> >&g

Re: [Marketing Mail] can't make any permissions change in 2.2.4

On Fri, Dec 18, 2015 at 8:55 AM, Reynald Bourtembourg < reynald.bourtembo...@esrf.fr> wrote: > This does not seem to be explained in the Cassandra 2.2 Upgrading section > of the NEWS.txt file: > > >

Data loss bug in upgrade to 3.0

We have discovered a critical bug for upgrade in the 3.0.0, 3.0.1 and 3.1 release. This bug, https://issues.apache.org/jira/browse/CASSANDRA-10822, only affects upgrades from a 2.x version (to any of the currently released 3.x version) and might cause data loss. As such, we strongly advice waiting

Re: lightweight transactions with potential problem?

Paxos phase, it > depends on CL in Cassandra? > > Ibrahim > > On Wed, Aug 26, 2015 at 11:50 AM, Sylvain Lebresne > wrote: > >> On Wed, Aug 26, 2015 at 12:19 PM, ibrahim El-sanosi < >> ibrahimsaba...@gmail.com> wrote: >> >>> Yes, Sylvain

Re: lightweight transactions with potential problem?

On Wed, Aug 26, 2015 at 12:19 PM, ibrahim El-sanosi < ibrahimsaba...@gmail.com> wrote: > Yes, Sylvain, your answer makes more sense. The phase is in Paxos protocol > sometimes called learning or decide phase, BUT this phase does not have > acknowledgment round, just learning or decide message from

Re: lightweight transactions with potential problem?

> By the way, I do not understand why in lightweight transactions in > Cassandra has round-trip commit/acknowledgment? > > For me, I think we can commit the value within phase propose/accept. Do > you agree? If not agree can you explain why we need commit/acknowledgment? > No, value cannot be comm

Re: lightweight transactions with potential problem?

this case, the important property is that they also promise to not "accept" any older ballot. > > I wish you could make it more clear. > > Thank you a lot Sylvain > > Ibrahim > > > On Tue, Aug 25, 2015 at 1:40 PM, Sylvain Lebresne > wrote: > >>

Re: lightweight transactions with potential problem?

That scenario cannot happen. More specifically, your step 12 cannot happen if step 8 has happen. Or more precisely, you got step 8 wrong: when a replica PROMISE, the promise is not that they won't "promise" a ballot older than 2, it's that they won't "accept" a ballot older than 2. Therefore, after

Re: JSON Cassandra 2.2 - insert syntax

Well, your column is not called "address", it's called "addresses". It's your type that is called "address". On Tue, Jun 2, 2015 at 4:39 AM, Michel Blase wrote: > Zach, > > this is embarrassing.you were right, I was running 2.1 > > shame on me! but now I'm getting the error: > > *Invalid

Re: Batch isolation within a single partition

On Tue, May 19, 2015 at 9:42 AM, DuyHai Doan wrote: > If RF > 1, the consistency level at QUORUM cannot guarantee strict > isolation (for normal mutation or batch). If you look at this slide: > http://www.slideshare.net/doanduyhai/cassandra-introduction-apache-con-2014-budapest/25, > you can see

Re: Data stax object mapping and lightweight transactions

This is very much a Java Driver question so please try to use the java driver mailing list ( https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user) for this type of question instead of the general Cassandra mailing list in the future. That said, to answer you question, no,

Re: sstable writer and creating bytebuffers

hat in general, if you have only a single column, then there isn't too much reasons to use a CompositeType. -- Sylvain > > > > *From:* Sylvain Lebresne [mailto:sylv...@datastax.com] > *Sent:* Monday, March 30, 2015 1:57 PM > *To:* user@cassandra.apache.org > *Subject:* Re

Re: sstable writer and creating bytebuffers

No, it's not a bug. In a composite every elements start by a 2 short indicating the size of the element, plus an extra byte that is used for sorting purposes. A little bit more details can be found in the CompositeType class javadoc if you're interested. It's not the most compact format there is bu

Re: BytesType and UTF8Type

On Fri, Jan 23, 2015 at 5:28 PM, Ken Hancock wrote: > > I have some thrift column families that were created with BytesType. All > the data written to the keys/columns/values were simple string. > > In cassandra-cli, I can "correct" these to UTF8Type (I believe both > UTF8Type and BytesType are

Re: Re: Dynamic Columns

> Where we differ that I feel the coverage for existing thrift use cases isn't > 100%. That may be right or wrong, but it is my impression. Here's my problem: either CQL covers all existing thrift use cases or it does not (in which case the non supported use case should be pointed out). It's a tec

Re: Re: Dynamic Columns

ft once you know and understand CQL well, but learning both is imo a bad advice. It could maybe (maybe) be justified if what you say about having whole family of use cases not being doable with CQL was true, but it's not. -- Sylvain > > > > On Wed, Jan 21, 2015 at 11:45 A

Re: Re: Dynamic Columns

On Wed, Jan 21, 2015 at 4:44 PM, Peter Lin wrote: > I don't remember other people's examples in detail due to my shitty > memory, so I'd rather not misquote. > Fair enough, but maybe you shouldn't use "people's examples you don't remenber" as argument then. Those examples might be wrong or outda

Re: Re: Dynamic Columns

> I've chatted with several long time users of Cassandra and there's things > CQL3 doesn't support. > Would you care to elaborate then? Maybe a simple example of something (or multiple things since you used plural) in thrift that cannot be supported in CQL? And please note that I'm *not* saying th

Re: row cache hit is costlier for partiton with large rows

The row cache saves partition data off-heap, which means that every cache hit require copying/deserializing the cached partition into the heap, and the more rows per partition you cache, the long it will take. Which is why it's currently not a good cache too much rows per partition (unless you know

Re: Re: Dynamic Columns

On Wed, Jan 21, 2015 at 3:46 AM, Peter Lin wrote: > > I don't understand why people [...] pretend it supports 100% of the use > cases. > Have you consider the possibly that it's actually true and you're just wrong by lack of knowledge? -- Sylvain

Re: "Not enough replica available” when consistency is ONE?

On Mon, Jan 19, 2015 at 2:29 AM, Kevin Burton wrote: > So ConsistencyLevel.ONE and if not exists are essentially mutually > incompatible and shouldn’t the driver throw an exception if the user > requests this configuration? > The subtlety is that this consistency level (CL.ONE in your case) is

Re: Token function in CQL for composite partition key

On Wed, Jan 7, 2015 at 10:18 AM, Ajay wrote: > Hi, > > I have a column family as below: > > (Wide row design) > CREATE TABLE clicks (hour text,adId int,itemId int,time timeuuid,PRIMARY > KEY((adId, hour), time, itemId)) WITH CLUSTERING ORDER BY (time DESC); > > Now to query for a given Ad Id and

Re: is primary key( foo, bar) the same as primary key ( foo ) with a ‘set' of bars?

On Sun, Jan 4, 2015 at 12:48 AM, Sylvain Wallez wrote: > Indeed this makes sense for map keys and set values, but AFAIU from the > docs this also applies to map and list _values_: " The maximum size of an > item in a collection is 64K" > Somehow it appears that from Jack's quote you've only rea

Re: IF NOT EXISTS on UPDATE statements?

On Mon, Nov 17, 2014 at 10:52 PM, Kevin Burton wrote: > There’s still a lot of weirdness in CQL. > > For example, you can do an INSERT with an UPDATE .. .which I’m generally > fine with. Kind of make sense. > > However, with INSERT you can do IF NOT EXISTS. > > … but you can’t do the same thing

Re: Empty cqlsh cells vs. null

On Mon, Oct 27, 2014 at 11:05 AM, Jens Rantil wrote: > Tyler, > > I see. That explains it. Any chance you might know how the Datastax Java > driver behaves for this (odd) case? > The Row.getInt() method will do as for nulls and return 0 (though of course, the Row.isNull() method will return fal

[RELEASE] Apache Cassandra 2.0.11 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.0.11. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source a

[RELEASE] Apache Cassandra 2.1.1 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.1.1. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source an

Re: Not-Equals (!=) in Where Clause

!= 0; > > On Tue, Sep 30, 2014 at 2:36 AM, Sylvain Lebresne > wrote: > >> >> >>> Is != supported as part of the where clause in Cassandra? >>> >> >> It's not. >> >> Or is it the grammar for some other purpose? >>> >

Re: Saving file content to ByteBuffer and to column does not retrieve the same size of data

On Tue, Sep 30, 2014 at 2:25 AM, Robert Coli wrote: > On Mon, Sep 22, 2014 at 3:50 AM, Carlos Scheidecker > wrote: > >> I can successfully read a file to a ByteBuffer and then write to a >> Cassandra blob column. However, when I retrieve the value of the column, >> the size of the ByteBuffer ret

Re: Not-Equals (!=) in Where Clause

> > Is != supported as part of the where clause in Cassandra? > It's not. Or is it the grammar for some other purpose? > It's supported in 'IF' conditions. You can do something like: SELECT * FROM foo WHERE k = 0 IF v != 3; -- Sylvain

[RELEASE] Apache Cassandra 2.1.0

The Cassandra team is pleased to announce the release of the final version of Apache Cassandra 2.1.0. Cassandra 2.1.0 brings a number of new features and improvements including (but not limited to): - Improved support of Windows. - A new incremental repair option[4, 5] - A better row cache that

[RELEASE CANDIDATE] Apache Cassandra 2.1.0-rc7 released

The Cassandra team is pleased to announce the sixth release candidate for the future Apache Cassandra version 2.1.0. Please note that this is not yet the final 2.1.0 release and as such, it should not be considered for production use. We'd appreciate testing and let us know if you encounter any pr

Re: Help with migration from Thrift to CQL3 on Cassandra 2.0.10

On Sun, Aug 31, 2014 at 2:59 AM, Todd Nine wrote: > Hi all, > I'm working on transferring our thrift DAOs over to CQL. It's going > well, except for 2 cases that both use multi get. The use case is very > simple. It is a narrow row, by design, with only a few columns. When I > perform a mul

Re: CQL performance inserting multiple cluster keys under same partition key

On Tue, Aug 26, 2014 at 6:50 PM, Jaydeep Chovatia < chovatia.jayd...@gmail.com> wrote: > Hi, > > I have question on inserting multiple cluster keys under same partition > key. > > Ex: > > CREATE TABLE Employee ( > deptId int, > empId int, > name varchar, > address varchar, > salary int

[RELEASE] Apache Cassandra 2.0.10 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.0.10. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source a

Re: Best way to format a ResultSet / Row ?

This kind of question belong to the java driver mailing list, not the Cassandra one, please try to use the proper mailing list in the future. On Tue, Aug 19, 2014 at 10:11 AM, Fabrice Larcher wrote: > > But this is probably not very usefull, since you get only prints of bytes. > You can then tes

[RELEASE CANDIDATE] Apache Cassandra 2.1.0-rc6 released

The Cassandra team is pleased to announce the sixth release candidate for the future Apache Cassandra version 2.1.0. Please note that this is not yet the final 2.1.0 release and as such, it should not be considered for production use. We'd appreciate testing and let us know if you encounter any pr

Re: range query times out (on 1 node, just 1 row in table)

That sounds like a bug (the trace does look fishy). I'm not sure you've indicated the Cassandra version you use so the first thing might be to check that this hasn't been fixed in a recent version, but if you are using a recent release (say 2.0.9), then please do open a JIRA ticket with your reprod

Re: C* 2.1-rc2 gets unstable after a 'DROP KEYSPACE' command ?

It would be nice if you can try with 2.1.0-rc5 (there has been quite a bit of bug fixes since rc2). If you can still reproduce that NPE there, please do open a jira ticket with the reproduction steps. On Thu, Aug 7, 2014 at 11:29 AM, Fabrice Larcher wrote: > Hello, > > After a 'DROP TABLE' comm

Re: Issue with ALLOW FILTERING

On Wed, Aug 6, 2014 at 9:41 AM, Jens Rantil wrote > > I'm struggling to see any reason for it not being supported. > The time to implement it, plus a bunch of internal implementation reasons that makes it not as trivial to support as you seem to suggest it is (of course, this is open source, you

Re: A question about using 'update keyspace with strategyoptions' command

agreement between nodes. > Not the *data* change. > > > > e.g. say I run the command ‘update keyspace with strategy_opitons [dc1: 3, > dc2:3]’ , when this command returns, > > are the *strategy* options already changed? Or I need to wait some time > for the strategy to be

Re: A question about using 'update keyspace with strategyoptions' command

Changing the strategy options, and in particular the replication factor, does not perform any data replication by itself. You need to run a repair to ensure data is replicated following the new replication. On Tue, Aug 5, 2014 at 10:52 AM, Lu, Boying wrote: > Thanks. yes. I can use the ‘show ke

[RELEASE CANDIDATE] Apache Cassandra 2.1.0-rc5 released

The Cassandra team is pleased to announce the release of the fifth release candidate for the future Apache Cassandra 2.1.0. If all goes well this candidate will become the final 2.1.0 but until then, it should not be considered for production use. We'd appreciate testing and let us know if you enc

[RELEASE CANDIDATE] Apache Cassandra 2.1.0-rc3 released

The Cassandra team is pleased to announce the release of the second release candidate for the future Apache Cassandra 2.1.0. Let first stress that this is not yet the final release of 2.1.0 and as such is *not* ready for production use. We however encourage as much testing as possible of this rele

[RELEASE] Apache Cassandra 1.2.18 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 1.2.18. Cassandra is a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. You can read more here: http://cassan

Re: [RELEASE] Apache Cassandra 1.2.17 released

java 6 and there no particular problem running them with java 6. With the one exception being the the new Cloudstack snitch introduced by CASSANDRA-7147 that will not work (it will throw a ClassNotFoundException) with java 6 until 1.2.18 is released. -- Sylvain On Mon, Jun 30, 2014 at 10:56 AM,

[RELEASE] Apache Cassandra 2.0.9 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.0.9. Cassandra is a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. You can read more here: http://cassand

[RELEASE] Apache Cassandra 1.2.17 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 1.2.17. Cassandra is a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. You can read more here: http://cassan

[RELEASE CANDIDATE] Apache Cassandra 2.1.0-rc2 released

The Cassandra team is pleased to announce the release of the second release candidate for the future Apache Cassandra 2.1.0. Let first stress that this is not yet the final release of 2.1.0 and as such is *not* ready for production use. We however encourage as much testing as possible of this rele

Re: repair takes 10x more time in one DC compared to the other

ice to have, we're just saying that this currently doesn't work and so we disallow it for now so people like you don't get bitten. If you have a patch to fix it ready, please do feel free to contribute. -- Sylvain > > > On Wed, Jun 25, 2014 at 1:48 PM, Sylvain Lebresne &g

Re: Does the default LIMIT applies to automatic paging?

ng it out. -- Sylvain > > > On Wed, Jun 25, 2014 at 12:21 AM, Sylvain Lebresne > wrote: > >> On Tue, Jun 24, 2014 at 1:03 AM, ziju feng wrote: >> >>> >>> I was wondering if the default 1 rows LIMIT applies to automatic >>> pagination

Re: repair takes 10x more time in one DC compared to the other

h "-pr" option? > > In any case, I'm using both "-local" and "-pr" options, what is the > expected behavior in that case? > > Cheers, > > > > On Wed, Jun 25, 2014 at 12:46 PM, Sylvain Lebresne > wrote: > >> TL;DR, this is not

Re: repair takes 10x more time in one DC compared to the other

TL;DR, this is not unexpected and this is perfectly fine. For every node, 'repair --local' will repair the "primary" (where primary means "the first range on the ring picked by the consistent hashing for this node given its token", nothing more) range of the node in the ring. And that range will b

Re: Storing values of mixed types in a list

On Wed, Jun 25, 2014 at 8:49 AM, Tuukka Mustonen wrote: > Unfortunately, I need to query per list items. That's why I'm running > Cassandra 2.1rc1 (offers secondary indexes for collections). > Using a list of blobs does not in any way prevent you from doing that. Types are constraints on what va

Re: Does the default LIMIT applies to automatic paging?

On Tue, Jun 24, 2014 at 1:03 AM, ziju feng wrote: > > I was wondering if the default 1 rows LIMIT applies to automatic > pagination in C* 2.0 (I'm using Datastax driver). > There is no "1 rows LIMIT" in CQL. cqlsh does apply a default LIMIT if you don't provide for convenience sake, but

Re: Use Cassnadra thrift API with collection type

On Mon, Jun 23, 2014 at 6:19 PM, James Campbell < ja...@breachintelligence.com> wrote: > Huilang, > > > Since there hasn't been another reply yet, I'll throw out an idea that > worked for us as part of a test, though it does not seem exactly like a > "preferred" way since it crosses code-bases.

Re: Exception with java driver

Please don't post on two mailing lists at once, it makes it impossible for people that are not subscribed to the 2 mailing list to follow the thread (and is bad form in general). If unsure which one is the most appropriate, it's fine, pick your best guest (in this case it's clearly a java driver qu

Re: Questions about timestamp set at writetime

> > 1) Who is responsible for this micro-second timestamp ? The coordinator > which receives the insert request or each replica which actually do persist > the data ? > The coordinator. > > 2) In a case of a batch insert (CQL3 batch, not batch mutation Thrift > API), if no user defined timestamp

[RELEASE CANDIDATE] Apache Cassandra 2.1.0-rc1 released

The Cassandra team is pleased to announce the release of the first release candidate for the future Apache Cassandra 2.1.0. Let first stress that this is not yet the final release of 2.1.0-rc1 and as such is *not* ready for production use. We however encourage as much testing as possible of this r

[RELEASE] Apache Cassandra 2.0.8 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.0.8. Cassandra is a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. You can read more here: http://cassand

[BETA RELEASE] Apache Cassandra 2.1.0-beta2 released

The Cassandra team is pleased to announce the release of the 2nd beta for the future Apache Cassandra 2.1.0. Let first stress that this is beta software and as such is *not* ready for production use. The goal of this release is to give a preview of what will become Cassandra 2.1 and to get wider

[RELEASE] Apache Cassandra 2.0.7 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.0.7. Cassandra is a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. You can read more here: http://cassand

Re: Dead node appearing in datastax driver

e to dispatch queries, that might impact latency I suppose -- at least that's the only related thing I can think of). -- Sylvain On Tue, Apr 1, 2014 at 2:44 PM, Apoorva Gaurav wrote: > Did that and I actually see a significant reduction in write latency. > > > On Tue, Apr 1, 2014 at

Re: Dead node appearing in datastax driver

be here). -- Sylvain > > On Tue, Apr 1, 2014 at 5:06 PM, Sylvain Lebresne wrote: > >> On Tue, Apr 1, 2014 at 12:50 PM, Apoorva Gaurav < >> apoorva.gau...@myntra.com> wrote: >> >>> Hello All, >>> >>> We had a 4 node cassandra 2.0.4 cl

Re: Dead node appearing in datastax driver

On Tue, Apr 1, 2014 at 12:50 PM, Apoorva Gaurav wrote: > Hello All, > > We had a 4 node cassandra 2.0.4 cluster ( lets call them host1, host2, > host3 and host4), out of which we've removed one node (host4) using > nodetool removenode command. Now using nodetool status or nodetool ring we > no lo

[RELEASE] Apache Cassandra 1.2.16 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 1.2.16. Cassandra is a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. You can read more here: http://cassan

Re: Thrift -> CQL

> > - *Is there any way to do insert / update at all on a good old wide cf > using CQL? Based on what we read back out, we have tried:* > > > INSERT INTO cf_name(key, column1, value) VALUES ('key1', > 'columnName1','columnValue2') > > > But we ended up with "Unknown identifier column1" > What d

Re: Serial Consistency and Thrift API

On Fri, Mar 14, 2014 at 7:59 PM, Panagiotis Garefalakis wrote: > > Hello all, > > I am running some tests in my cluster and I wanted to try some of the new > features of Cassandra like lightweight transactions and Serial Writes. > Surprisingly I found out that Serial writes are not supported by th

Re: CQL Select Map using an IN relationship

On Thu, Mar 13, 2014 at 12:12 PM, David Savage wrote: > Hi there, > > I'm experimenting using cassandra and have run across an error message > which I need a little more information on. > > The use case I'm experimenting with is a series of document updates > (documents being an arbitrary map of k

[RELEASE] Apache Cassandra 2.0.6 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 2.0.6. Cassandra is a highly scalable second-generation distributed database, bringing together Dynamo's fully distributed design and Bigtable's ColumnFamily-based data model. You can read more here: http://cassand

Re: Question regarding java DowngradingConsistencyRetryPolicy

Let me first note that the DataStax Java driver has a dedicated mailing list: https://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user, it would better to use that list for driver specific questions in the future. But to answer your question, a SIMPLE write is any write (INSER

Re: Invalid compacted_at timestamp entries in Cassandra 2.0.5

You're probably running into https://issues.apache.org/jira/browse/CASSANDRA-6784. This will be fixed in 2.0.6. On Mon, Mar 3, 2014 at 3:43 PM, Phil Luckhurst < phil.luckhu...@powerassure.com> wrote: > Running 'nodetool compactionHistory' seems to be showing strange timestamp > values for the 'c

Re: Combine multiple SELECT statements into one RPC?

On Thu, Feb 27, 2014 at 1:00 AM, Clint Kelly wrote: > Hi all, > > Is there any way to use the DataStax Java driver to combine multiple > SELECT statements into a single RPC? I assume not (I could not find > anything about this in the documentation), but I just wanted to check. > The short answe

Re: Update multiple rows in a CQL lightweight transaction

Sylvain > > (This scenario may not matter to most folks, which is totally fine, I just > want to make sure that I understand.) > > Should I instead look into using the Thrift API to address this? > > Best regards, > Clint > > > > On Tue, Feb 25, 2014 at 11:3

Re: Update multiple rows in a CQL lightweight transaction

Sorry to interfere again here but CASSANDRA-5633 will not be picked up because pretty much everything it was set to fix is fixed by CASSANDRA-6561, this is *not* a syntax problem anymore. On Wed, Feb 26, 2014 at 3:18 AM, Tupshin Harper wrote: > Unfortunately there is no option to vote for a "re

  1   2   3   4   5   6   7   8   >