Bloom filter is stored in RAM, but what about metadata?
Is disk seek required to access it?
No, it's loaded in RAM when the sstable is loaded.
--
Sylvain
To add to Aaron response, you can update a CF concurrently in 1.1
already. However, you cannot create multiple CF concurrently just yet,
but that will be fixed in 1.2.
--
Sylvain
On Sun, Aug 26, 2012 at 11:04 PM, aaron morton aa...@thelastpickle.com wrote:
Concurrent schema changes are coming
but
*not* for creation (if you create CF concurrently, whether that is the
same CF or not, you might have problem). The last part will be fixed
in 1.2 however.
--
Sylvain
вторник, 4 сентября 2012 г. пользователь Sylvain Lebresne писал:
To add to Aaron response, you can update a CF concurrently in 1.1
Is there a way to fix this error ? What is its impact on my data ?
The fact that the message shows means that Cassandra has attempted to
repair the problem so there isn't much to do. However the fact that
you do get the messages in the first means that there is a bug
somewhere that generate
not agree about schema exception on later node ? something worse?
2012/9/5 Sylvain Lebresne sylv...@datastax.commailto:sylv...@datastax.com
On Tue, Sep 4, 2012 at 8:23 PM, Илья Шипицин
chipits...@gmail.commailto:chipits...@gmail.com wrote:
Is it ok multiple servers will create/update the same CF
That obviously shouldn't happen and I don't remember any open ticket
related to that. You might want to open a ticket on jira
(https://issues.apache.org/jira/browse/CASSANDRA).
--
Sylvain
On Fri, Sep 7, 2012 at 10:50 AM, B R software.research.w...@gmail.com wrote:
We have upgraded a 0.8 cluster
Is there any way of updating the TTL without being in need of rewriting the
data back again?
No, there isn't.
If not, is running a Map/Reduce task on the whole data set the best option
If the TTL is made rather infrequently and on a large percentage of
the data, which seems to be your
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.1.5.
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:
Is every string/id combination stored separately in disk
Yes, each combination is stored separately on disk (the storage engine
itself doesn't have special casing for composite column, at least not
yet). But as far as disk space is concerned, I suspect that sstable
compression makes this largely
Cassandra version. First thing you should do is
to finish the upgrade of the nodes.
--
Sylvain
On Fri, Sep 7, 2012 at 9:11 PM, Sylvain Lebresne sylv...@datastax.com
wrote:
That obviously shouldn't happen and I don't remember any open ticket
related to that. You might want to open a ticket
Is there any JIRA or enhancement to perhaps be able to detect when certain
column tombstones can be deleted in minor compactions? The new introduction
of SSTable min-max timestamps might help? or perhaps there are new ones
coming up that I'm not aware of
Range queries do not use bloom filters. It holds good for composite-columns
also right?
Since I assume you are referring to column's bloom filters (key's bloom filters
are always used) then yes, that holds good for composite columns. Currently,
composite column name are completely opaque to the
I wrote an answer on the blog post
(http://www.datastax.com/dev/blog/cql3_collections#comment-127093).
--
Sylvain
On Thu, Sep 20, 2012 at 7:13 AM, Roshni Rajagopal
roshni_rajago...@hotmail.com wrote:
Hi,
CQL3, has collections support as described in this link
On Wed, Sep 19, 2012 at 2:00 PM, Roshni Rajagopal
roshni_rajago...@hotmail.com wrote:
Hi,
There was a conversation on this some time earlier, and to continue it
Suppose I want to associate a user to an item, and I want to also store 3
commonly used attributes without needing to go to an
On Wed, Sep 19, 2012 at 3:32 PM, Brian O'Neill b...@alumni.brown.edu wrote:
That said, I'm keeping a close watch on:
https://issues.apache.org/jira/browse/CASSANDRA-3647
But if this is CQL only, I'm not sure how much use it will be for us
since we're coming in from different clients.
Anyone
As I understand from the link below, burning column index-info onto the
sstable index files will not only eliminate sstables but also reduce disk
seeks from 3 to 2 for wide rows.
Yes.
Shouldn't we be wary of the spike in heap usage by promoting column indexes
to index file?
If you're
In CQL3, names are case insensitive by default, while they were case
sensitive in CQL2. You can force whatever case you want in CQL3
however using double quotes. So in other words, in CQL3,
USE TestKeyspace;
should work as expected.
--
Sylvain
On Sun, Sep 23, 2012 at 9:22 PM, Oleksandr Petrov
On Sun, Sep 23, 2012 at 11:30 PM, aaron morton aa...@thelastpickle.com wrote:
If this is intended behavior, could somebody please point me to where this
is
documented?
It is intended.
It is not in fact. We should either refuse the query as yet
unsupported or we should do the right thing, but
The Cassandra team is pleased to announce the release of the first beta for
the future Apache Cassandra 1.2.0.
Let me 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
1.2 and to get
So general question, should I rely on Counters if I want 100% accuracy?
No.
Even not considering potential bugs, counters being not idempotent, if you
get a TimeoutException during a write (which can happen even in relatively
normal conditions), you won't know if the increment went in or not
went true: the ones that timeout
may or may have been persisted.
--
Sylvain
Though as you mention, there would be no way to repair your dropped
messages .
On Tue, Sep 25, 2012 at 6:57 PM, Sylvain Lebresne sylv...@datastax.com
wrote:
So general question, should I rely on Counters if I want
You're mistaking 'key validation class' and 'comparator'. It is your
key validation class that is DecimalType. Your comparator is UTF8Type,
and yes, switching the comparator from UTF8Type to DecimalType is not
allowed.
--
Sylvain
On Tue, Sep 25, 2012 at 10:13 PM, Hiller, Dean
On Wed, Sep 26, 2012 at 2:35 AM, Rob Coli rc...@palominodb.com wrote:
150,000 sstables seem highly unlikely to be performant. As a simple
example of why, on the read path the bloom filter for every sstable
must be consulted...
Unfortunately that's a bad example since that's not true.
Leveled
When people suggest composites instead of super columns, they mean
composite column 'names', not composite column 'values'. None of the
advantages you cite stand in the case of composite column 'names'.
--
Sylvain
On Wed, Sep 26, 2012 at 11:52 PM, Edward Kibardin infa...@gmail.com wrote:
Hi
On Thu, Sep 27, 2012 at 12:13 AM, Hiller, Dean dean.hil...@nrel.gov wrote:
We are streaming data with 1 stream per 1 CF and we have 1000's of CF. When
using the tools they are all geared to analyzing ONE column family at a time
:(. If I remember correctly, Cassandra supports as many CF's as
I can verify the existence of the key that was inserted in Commitlogs of both
replicas however it seams that this record was never inserted.
Out of curiosity, how can you verify that?
--
Sylvain
The node tool cfstats, what is the row count estimate usually off by(what
percentage? Or what absolute number?)
It will likely not be very good but is supposed to give some order of
magnitude. That being said there is at least the following sources of
inaccuracies:
- It counts deleted rows
But from my understanding, you just can't update composite column, only
delete and insert... so this may make my update use case much more
complicated.
Let me try to sum things up.
In regular column families, a column (value) is defined by 2 keys: the
row key and the column name.
In super
I don't understand why it copied data twice. In worst case scenario it
should copy everything (~90G)
Sadly no, repair is currently peer-to-peer based (there is a ticket to
fix it: https://issues.apache.org/jira/browse/CASSANDRA-3200, but
that's not trivial). This mean that you can end up with
I see. It explains why I get 85G + 85G instead of 90G. But after next
repair I have six extra files 75G each,
how is it possible?
Maybe you've run repair on other nodes? Basically repair is a fairly
blind process. If it consider that a given range (and by range I mean
here the ones that repair
Sure.
On Mon, Oct 1, 2012 at 5:33 PM, Jonathan Rudenberg
jonat...@titanous.com wrote:
Thanks. Do you want me to open a JIRA ticket?
On Oct 1, 2012, at 2:45 AM, Sylvain Lebresne sylv...@datastax.com wrote:
Ok, I'll look what's wrong.
--
Sylvain
Could you create one ?
https://issues.apache.org/jira/browse/CASSANDRA
There's one already. See
https://issues.apache.org/jira/browse/CASSANDRA-3702 that redirect to
https://issues.apache.org/jira/browse/CASSANDRA-4415.
--
Sylvain
It's in the 1.1 branch; I don't remember if it went into a release
yet. If not, it'll be in the next 1.1.x release.
As the ticket says, this is in since 1.1.1. I don't pretend this is
well documented, but it's in.
--
Sylvain
The short version is: there is 2 use case for nodetool repair:
1) For periodic repair of the whole cluster
(http://wiki.apache.org/cassandra/Operations#Frequency_of_nodetool_repair).
In that case, you should run repair *with* -pr and you should run it
on *every* node.
2) When a node has been
So, I suspect I can expect those rows to finally go away when queried from
cassandra-cli once GCGraceSeconds has passed then?
Yes.
--
Sylvain
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.0.12.
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:
For the Parisian out there, we're having the 2nd installment of the
Paris Cassandra Meetup next Thursday (October 11).
This time, we'll have Matt Dennis coming all the way from Austin to
talk about Apache Cassandra data model differences compared to
RDBMS.
You don't want to miss that so go see
Is it not possible to include a column in both the set clause and in the
where clause?
No it's not. Or rather in that case what is not supported is the use
of secondary indexes in update where clauses. But if 'locked' is
indeed not part of your primary key, then at least the error message
suck
On Tue, Oct 9, 2012 at 3:59 AM, Vivek Mishra mishra.v...@gmail.com wrote:
it is giving me an error:
[timestamp out of range for platform time_t]
Hum, I can't reproduce that with the current 1.1 branch (nor in
trunk). So my bet is that this was an error from cqlsh that has been
fixed recently.
Yeah, you might want to check 1.1.5, 1.1.2 is so ancient :)
--
Sylvain
On Tue, Oct 9, 2012 at 9:44 AM, Vivek Mishra mishra.v...@gmail.com wrote:
I am trying it with 1.1.2 cassandra release.
-Vivek
On Tue, Oct 9, 2012 at 1:13 PM, Sylvain Lebresne sylv...@datastax.com
wrote:
On Tue
On Tue, Oct 9, 2012 at 8:57 AM, Vivek Mishra mishra.v...@gmail.com wrote:
Ok. I am able to understand the problem now. Issue is:
If i create a column family altercations as:
**8
CREATE
?
Thanks,
Sylvain
-Vivek
On Tue, Oct 9, 2012 at 1:16 PM, Sylvain Lebresne sylv...@datastax.com
wrote:
On Tue, Oct 9, 2012 at 8:57 AM, Vivek Mishra mishra.v...@gmail.com
wrote:
Ok. I am able to understand the problem now. Issue is:
If i create a column family altercations
I have a question about merkle tree construction and repair process. When
mercle tree is constructing it calculates hashes. For DeletedColumn it
calculates hash using value. Value of DeletedColumn is a serialized local
deletion time.
The deletion time time is not local to each replica, it's
On Fri, Oct 12, 2012 at 7:51 PM, Sridharan Kuppa
sridharan.ku...@outlook.com wrote:
Hi,
I have created table schema using CQL, and I am able to insert and select
from that table. Everything works great but DELETE is not working. When I
execute the DELETE statement it throws Bad Request:
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.1.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:
on
http://www.apache.org/dist/cassandra/, but other mirror can easily lag
behind.
I do have messed up in the past, but it seems to be a mirror not in
sync problem since I've been able to get it with some mirrors.
--
Sylvain
On 10/15/12 9:46 AM, Sylvain Lebresne sylv...@datastax.com wrote
On Tue, Oct 16, 2012 at 11:57 AM, Vivek Mishra mishra.v...@gmail.com wrote:
---
RowKey: Jayne Cobb
= (column=2012-07-24:2:alliance_involvement, value=false,
timestamp=135038100502)
= (column=2012-07-24:2:energy_used, value=4.6, timestamp=1350381005020001)
Not sure, why
On Tue, Oct 16, 2012 at 12:31 PM, Vivek Mishra mishra.v...@gmail.com wrote:
Thanks Sylvain. I missed it. If i try to access these via thrift API, what
will be the column names?
I'm not sure I understand the question. The cli output is pretty much
what you get via the thrift API.
--
Sylvain
, Sylvain Lebresne sylv...@datastax.com
wrote:
On Tue, Oct 16, 2012 at 12:31 PM, Vivek Mishra mishra.v...@gmail.com
wrote:
Thanks Sylvain. I missed it. If i try to access these via thrift API,
what
will be the column names?
I'm not sure I understand the question. The cli output is pretty much
, Oct 17, 2012 at 1:04 PM, Sylvain Lebresne sylv...@datastax.com
wrote:
On Wed, Oct 17, 2012 at 3:17 AM, Vivek Mishra mishra.v...@gmail.com
wrote:
column name will be 2012-07-24:2:alliance_involvement or
alliance_involvement?
The former. Though let's clarify that
2012-07-24:2
The data does get removed as soon as possible (as soon as it is
compacted with the tombstone that is).
--
Sylvain
On Mon, Oct 22, 2012 at 7:03 PM, Hiller, Dean dean.hil...@nrel.gov wrote:
My understanding is any time from that node. Another node may have a
different existing value and
CQL3 does absolutely allow dynamic column families, but does it
differently from CQL2. See
http://www.datastax.com/dev/blog/cql3-for-cassandra-experts.
--
Sylvain
On Mon, Oct 29, 2012 at 12:34 PM, Timmy Turner timm.t...@gmail.com wrote:
Does CQL3 not allow dynamic columns (column names) any
On Tue, Oct 30, 2012 at 11:56 AM, Timmy Turner timm.t...@gmail.com wrote:
Does the cell transposition that is necessary for CQL3 happen on the
server side after the query execution, or is it something that the
Cassandra/CQL-client does before ultimately handing over the result
set to the
You didn't do anything wrong, it's how CQL3 works. I suggest having a
look at http://www.datastax.com/dev/blog/thrift-to-cql3. Especially
the section called Non compact tables might hopefully explains more.
--
Sylvain
On Wed, Oct 31, 2012 at 6:14 PM, Wei Zhu wz1...@yahoo.com wrote:
I try to use
The first thing I would check is if nodetool is using the right jar. I
sounds a lot like if the server has been correctly updated but
nodetool haven't and still use the old classes.
Check the nodetool executable, it's a shell script, and try echoing
the CLASSPATH in there and check it correctly
Is this a feature or a bug?
Neither really. Repair doesn't do any gcable tombstone collection and
it would be really hard to change that (besides, it's not his job). So
if you when you run repair there is sstable with tombstone that could
be collected but are not yet, then yes, they will be
On Sat, Nov 3, 2012 at 1:40 AM, Eric Evans eev...@acunu.com wrote:
On Fri, Nov 2, 2012 at 8:09 PM, Vivek Mishra mishra.v...@gmail.com wrote:
any idea, how to insert into a column family for a column of type blob via
cql query?
Yes, most of them involve binary data that is hex-encoded ascii.
On Fri, Nov 2, 2012 at 10:46 AM, horschi hors...@gmail.com wrote:
might I ask why repair cannot simply ignore anything that is older than
gc-grace? (like Aaron proposed)
Well, actually the merkle tree computation could probably ignore
gcable tombstones without much problem, which might not be
On Sat, Nov 3, 2012 at 10:23 PM, horschi hors...@gmail.com wrote:
Do you mind if I ask where you stand on making...
- ... ExpiringColumn not create any tombstones? Imo this could be safely
done if the columns TTL is = gcgrace.
Yes, if the TTL = gcgrace this would be safe and I'm pretty sure we
On Sun, Nov 4, 2012 at 7:49 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
CQL3 Allows me to search the second component of a primary key. Which
really just seems to be component 1 of a composite column.
So what thrift operation does this correspond to? This looks like a
column slice
You are free to use BytesType if you want, but adding meaningful types has
the advantage of adding a checked documentation of what is stored in your
CF. Or in other words:
- If multiple applications/users access the same CF, it's a documentation
on what you can expect to get and what you are
On Mon, Nov 5, 2012 at 10:53 AM, Maxim Veksler ma...@vekslers.org wrote:
Are indexes on composite column supported ?
Index on any part of the PRIMARY KEY is not supported (whether the PRIMARY
KEY is composite or not btw), not yet at least.
If not, a suggestion for a work around?
In your
On Mon, Nov 5, 2012 at 4:12 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
Is this query the equivalent of a full table scan? Without a starting
point get_range_slice is just starting at token 0?
It is, but that's what you asked for after all. If you want to start at a
given token you can
On Mon, Nov 5, 2012 at 2:11 PM, horschi hors...@gmail.com wrote:
I dont know what your approach was back then, but maybe it could be solved
quite easily: When creating tombstones for ExpiringColumns, we could use
the ExpiringColumn.timestamp to set the DeletedColumn.localDeletionTime .
So
On Mon, Nov 5, 2012 at 6:55 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
I see. It is fairly misleading because it is a query that does not
work at scale. This syntax is only helpful if you have less then a few
thousand rows in Cassandra.
Just for the sake of argument, how is that
this because as an end user I do not understand if a given query
is actually going to return the same results with different data.
On Mon, Nov 5, 2012 at 1:40 PM, Sylvain Lebresne sylv...@datastax.com
wrote:
On Mon, Nov 5, 2012 at 6:55 PM, Edward Capriolo edlinuxg...@gmail.com
wrote
The Cassandra team is pleased to announce the release of the second beta for
the future Apache Cassandra 1.2.0.
Let me first stress that this is beta software and as such is *not* ready
for
production use.
This release is still beta so is likely not bug free. However, lots have
been
fixed since
, 2012, at 9:27 PM, Edward Capriolo wrote:
just a note for all. The default partitioner is no longer
randompartitioner. It is now murmur, and the token range starts in negative
numbers. So you don't chose tokens Luke your father taught you anymore.
On Friday, November 9, 2012, Sylvain Lebresne
On Sat, Nov 10, 2012 at 7:17 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
No it does not exist. Rob and I might start a donation page and give
the money to whoever is willing to code it. If someone would write a
tool that would split an sstable into 4 smaller sstables (even an
offline
I've updated the readme, thanks
On Sun, Nov 11, 2012 at 6:49 PM, Jean-Armel Luce jaluc...@gmail.com wrote:
Hello,
I have installed the 1.2 beta2 (download source + compil)
The CREATE SCHEMA fails if I do as explained in README.txt :
bin/cqlsh --cql3== --cql3 is the default in 1.2 so
Parisian folks (for the others, sorry for the spam),
You will want to mark next Monday in your Agenda as we're having the 3rd
Paris Cassandra meetup. This time, Jonathan Ellis will be our speaker
(somehow we get more speakers from Texas than from Paris in this meetup, go
figure) who will present
On Mon, Nov 12, 2012 at 6:10 PM, Tyler Hobbs ty...@datastax.com wrote:
On Sun, Nov 11, 2012 at 4:21 AM, Sylvain Lebresne sylv...@datastax.comwrote:
Actually, if we're going to be precise, it's -2^63 to 2^63 - 1.
Long.MIN_VALUE is not a valid token for technical reasons.
I think you typo'd
It's not supported yet, no, but we have a ticket for it:
https://issues.apache.org/jira/browse/CASSANDRA-4511
On Mon, Nov 19, 2012 at 3:56 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
This was my first question after I git the inserts working. Hive has udfs
like array contains. It also has
Everyone,
We've just open-sourced a new Java driver we have been working on here at
DataStax. This driver is CQL3 only and is built to use the new binary
protocol
that will be introduced with Cassandra 1.2. It will thus only work with
Cassandra 1.2 onwards. Currently, it means that testing it
Currently, I'm not sure you can really reduce those dependencies. But we do
plan on reducing that ultimately. Basically the reason we have anything
thrift related in there is that so far we depends on the full Cassandra
jar. However, we'll pull out the classes uses by the native transport in
their
On Mon, Nov 26, 2012 at 8:41 AM, aaron morton aa...@thelastpickle.comwrote:
Is there any noticeable performance difference between thrift or CQL3?
Off the top of my head it's within 5% (maybe 10%) under stress tests. See
Eric's talk at the Cassandra SF conference for the exact numbers.
Eric's
Thanks for the answer ... the error described before is: ORDER BY is only
supported when the partition key is restricted by an EQ or an IN.
But I don't see how I didn't respect the rule ...
The error message is indeed somewhat misleading and I've just committed a
fix to return a better
Counters replication works in different ways than the one of normal
writes. Namely, a counter update is written to a first replica, then a read
is perform and the result of that is replicated to the other nodes. With
RF=1, since there is only one replica no read is involved but in a way it's
a
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.1.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:
To my understanding client will not be notified because this read step is
asynchronously.
Yes, though for the record it's actually synchronous if you use anything
else than CL.ONE.
Also the other replica cannot be updated properly (replicate-on-write
stage is backing up).
Question is:
-
The Cassandra team is pleased to announce the release of the third beta for
the future Apache Cassandra 1.2.0.
Let me first stress that this is beta software and as such is *not* ready
for
production use.
This release is still beta and as such may contain bugs. Any help testing
this beta would
On Mon, Dec 10, 2012 at 12:36 PM, Abhijit Chanda
abhijit.chan...@gmail.comwrote:
Hi All,
I have a column family which structure is
CREATE TABLE practice (
id text,
name text,
addr text,
pin text,
PRIMARY KEY (id, name)
) WITH
comment='' AND
caching='KEYS_ONLY' AND
What kind of official statement do you want? As far as I can be considered
an official voice of the project, my statement is: various people run in
production with Java 7 and it seems to work.
Or to answer the initial question, the only issue related to Java 7 that I
know of is CASSANDRA-4958,
problem, because
they don't support C* running on 7?
At least that would be one way of defining officially supported.
On Fri, Dec 14, 2012 at 2:22 AM, Sylvain Lebresne
sylv...@datastax.com wrote:
What kind of official statement do you want? As far as I can be
considered
an official
The Cassandra team is pleased to announce the first release candidate for
the
future Apache Cassandra 1.2.0.
Let me first stress that this is not the final release yet and as such is
*not*
ready for production use.
This release is getting very close to a final version but may still contain
bugs.
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.1.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:
This is almost surely due to
https://issues.apache.org/jira/browse/CASSANDRA-4813 which slightly changed
the stream on-wire format. If you first upgrade the rest of your cluster to
rc1, you should be fine.
On Thu, Dec 20, 2012 at 9:33 AM, Omar Shibli o...@eyeviewdigital.comwrote:
I've a
The Cassandra team is pleased to announce the second release candidate (and
likely the last Cassandra release ever since it's the end of the world) for
the
future Apache Cassandra 1.2.0.
Let me first stress that this is not the final release yet and as such is
*not*
ready for production use.
WHEN does Cassandra remove expired (because of TTL) data?
When a compaction reads an expired column, it removes it and replaces it by
a tombstone (i.e. a deleted marker). So the first compaction after the
expiration is what actually removes the data, but it won't reclaim all the
disk space yet
The Cassandra team wishes you a very happy new year 2013, and is very
pleased
to announce the release of Apache Cassandra version 1.2.0. Cassandra 1.2.0
is a
new major release for the Apache Cassandra distributed database. This
version
adds numerous improvements[1,2] including (but not restricted
On Thu, Jan 3, 2013 at 10:21 AM, Alain RODRIGUEZ arodr...@gmail.com wrote:
Does this mean that there absolutely no way to switch to the new
partitioner for people that are already using Cassandra ?
Yes, that is what this means.
--
Sylvain
On Mon, Jan 7, 2013 at 12:10 PM, Tristan Seligmann
mithra...@mithrandi.netwrote:
I am guessing the strange results you get are a bug; Cassandra should
either refuse to execute the query
That is correct. I've created
https://issues.apache.org/jira/browse/CASSANDRA-5122 and will attach a
patch
1. There are column types that correspond to types that are not defined by
the spec such as Boolean, UUID, Timestamp, Decimal, Double, Float etc..
Will
these types always a serialized java type? What happens if Java doesn't
define a size or byte order? Are these defined in a cassandra doc
Mostly this is because having the frame length is convenient to have in
practice.
Without pretending that there is only one way to write a server, it is
common
to separate the phase read a frame from the network from the phase decode
the frame which is often simpler if you can read the frame
There is no upgrade path.
I don't think that's true. The goal of the blog post you've linked is to
discuss that upgrade path (and in particular show that for the most part,
you
can access your thrift data from CQL3 without any modification whatsoever).
You adopt CQL3's sparse tables as soon as
On Sun, Jan 13, 2013 at 5:59 PM, Shahryar Sedghi shsed...@gmail.com wrote:
Since new cql3 methods require ConsistencyLevel.xxx, is consistency level
at the query has precedence over this level at the api or not.
There is no consistency level at the query level anymore. That's one of
the
On Mon, Jan 14, 2013 at 4:34 PM, Sylvain Lebresne sylv...@datastax.comwrote:
methods
columns.
--
Sylvain
-Vivek
On Mon, Jan 14, 2013 at 7:18 PM, Sylvain Lebresne sylv...@datastax.comwrote:
On Mon, Jan 14, 2013 at 12:48 PM, Vivek Mishra mishra.v...@gmail.comwrote:
I am getting an issue, where key attribute's in byte[] is returned as
empty value.
We don't return
On Mon, Jan 14, 2013 at 5:04 PM, Shahryar Sedghi shsed...@gmail.com wrote:
Can I always count on this order, or it may change in the future?
I would personally rely on it. I don't see any reason why we would change
that internally and besides I suspect you won't be the only one to rely on
it
We've fixed our fair share of bugs since 1.1.8 so I propose the following
artifacts for release as 1.1.9.
sha1: 7eb47c50c394f0aefdfd4ac9170ce51e2e4be549
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.9-tentative
Artifacts:
1 - 100 of 737 matches
Mail list logo
