I agree with your observations.
From another hand I found that ColumnFamily.size() doesn't calculate object
size correctly. It doesn't count two fields Objects sizes and returns 0 if
there is no object in columns container.
I increased initial size variable value to 24 which is size of two
Glad you've got it working properly. I've tried to make as local changes
as possible, so changed only single value calculation. But it's possible
your way is better and will be accepted by cassandra maintainer. Could you
attach your patch to the ticket. I'd like for any fix to be applied to the
Hi,
I've seen this blog entry:
http://www.datastax.com/dev/blog/schema-in-cassandra-1-1 and I am trying to
understand, how could Cassandra support PRIMARY KEY.
Cassandra has silent conflict resolution, where each insert overwrites next
one, and there are only inserts and deletes - no updates.
Hi,
With Cassandra 1.1, I have the following crash on a fresh new single node
cluster running on Windows 7.
On client side:
create keyspace toto;
create column family titi;
truncate titi;
The crash server side (the server is dead then) :
Yes, AFAIK it's still like this (and I don't think that this behavior will
change, you can rely on it).
Paolo
On Apr 25, 2012 9:36 AM, Maciej Miklas mac.mik...@googlemail.com wrote:
Hi,
I've seen this blog entry:
http://www.datastax.com/dev/blog/schema-in-cassandra-1-1 and I am trying
to
On Apr 25, 2012 9:36 AM, Maciej Miklas mac.mik...@googlemail.com wrote:
Hi,
I've seen this blog entry:
http://www.datastax.com/dev/blog/schema-in-cassandra-1-1 and I am trying to
understand, how could Cassandra support PRIMARY KEY.
Cassandra has silent conflict resolution, where each
Dne 18.4.2012 16:22, Jonathan Ellis napsal(a):
It's not that simple, unless you have an append-only workload.
I have append only workload and probably most ppl using TTL too.
De : aaron morton [mailto:aa...@thelastpickle.com]
The secondary index will be build using the compaction features,
you can check the progress with nodetool compactionstats
When they are build the output from describe. will list the build indexes.
Built indexes: []
Should I understand
CQL will have UPDATE future, I am trying to understand how this could work.
Every write is an append to SSTable, UPDATE would need to change data, but
only if it exists, and this is problematic, since we have distributed
system.
Is UPDATE special kind of insert, which changes given data only if
In CQL, both UPDATE AND INSERT have the same semantic and are both upsert.
I.e, INSERT does not fail if the record was already existing and
UPDATE does not fail if the record wasn't existing.
--
Sylvain
On Wed, Apr 25, 2012 at 1:18 PM, Maciej Miklas
mac.mik...@googlemail.com wrote:
CQL will
Tyler,
A think you could add this values as python constants to pycassa. This
would be very useful for many people.
2012/4/24 Drew Kutcharian d...@venarc.com
Nice, that's exactly what I was looking for.
On Apr 24, 2012, at 11:21 AM, Tyler Hobbs wrote:
Oh, I just realized that you're
Hi,
I see strange behaviour using CF with two secondary indexes, one
IntegerType one UTF8Type.
Using Cassanra 1.0.9 and CF:
create column family IndexTest
with column_type=Standard
and comparator=UTF8Type
and default_validation_class=UTF8Type
and key_validation_class=UTF8Type
I'll also try LongType index. I'll let you know how that works.
Regards,
P.
Hi
We have the such CF, and use secondary index to search for simple data
status, and among 1,000,000 row records, we have 200 records with status
we want.
But when we start to search, the performance is very poor, and check with
the command ./bin/nodetool -h localhost -p 8199 cfstats ,
And I found, if I only have the search condition status, it only scan 200
records.
But if I combine another condition partition then it scan all records
because partition condition match all records.
But combine with other condition such as userName, even all userName is
same in the 1,000,000
what version of cassandra are you using. I found a big performance hit
when querying on the secondary index.
I came across this bug in versions prior to 1.1
https://issues.apache.org/jira/browse/CASSANDRA-3545
Hope that helps.
2012/4/25 Jason Tang ares.t...@gmail.com
And I found, if I only
1.0.8
在 2012年4月25日 下午10:38，Philip Shon philip.s...@gmail.com写道：
what version of cassandra are you using. I found a big performance hit
when querying on the secondary index.
I came across this bug in versions prior to 1.1
https://issues.apache.org/jira/browse/CASSANDRA-3545
Hope that
De : mdione@orange.com [mailto:mdione@orange.com]
Should I understand that when the indexes are finished being built a)
the «Built indexes» list should be empty and b) there should be no pending
compactions? Because that's exactly what I have now but I still can't
use the column
How much data do you have and how long is a while? In my experience repairs
can take a very long time. Check to see if validation compactions are running
(nodetool compactionstats) or if files are streaming (nodetool netstats). If
either of those are in progress then your repair should be
Good idea. Done here:
https://github.com/pycassa/pycassa/commit/2390363066c7efd79bdd2f27cd2d4496f692abf4
On Wed, Apr 25, 2012 at 7:11 AM, Carlo Pires carlopi...@gmail.com wrote:
Tyler,
A think you could add this values as python constants to pycassa. This
would be very useful for many
has anybody written up anything related to recovery for fails in EC2?
this morning i woke up to find 1 (of 4) nodes marked as unreachable. i
used the datastax (1.0.7) ami to set up my cluster and the node that
fail had the token id of 0 (this is the seed node - right?). the docs
says to
0 is a perfectly valid id.node - 1 is modulo the maximum token value. that
token range is 0 - 2**127so node - 1 in this case is 2**127 - Original
Message -From: quot;Deno Vichasquot; ;d...@syncopated.net
Questions like this should be directed to the user mailing list
(user@cassandra.apache.org); This mailing list is for discussion of
development *of* Cassandra.
On Wed, Apr 25, 2012 at 3:25 PM, Benny Rönnhager
benny.ronnha...@thrutherockies.com wrote:
I am building a database with several hundred
Each node need its own HDD for multiple copies. cant share it with others
node.
On Thu, Apr 26, 2012 at 8:52 AM, Benny Rönnhager
benny.ronnha...@thrutherockies.com wrote:
Hi!
I am building a database with several hundred thousands of images.
have just learned that HaProxy is a very good
If your shared disk is super fast enough to handle IO requests from
multiple cassandra node, you can do it in theory. And the disk will be
the single point of failure in your system.
For optimal performance, each node should have at least 2 hdd, one for
commitlog and one for data.
maki
2012/4/26
25 matches
Mail list logo
