You have to log in and then you can create topic only below some sections
(opscenter, feedbacks, ...) if I remember well.
Alain
2013/8/1 yue.zhang yue.zh...@chinacache.com
thanks Alain
** **
I don’t know why not permited to create topic on datastax forum*.*
** **
** **
*发件人:*
On Wed, Jul 31, 2013 at 03:10:54PM -0700, Jonathan Haddad wrote:
It's advised you do not use compact storage, as it's primarily for
backwards compatibility.
Yes indeed, I understand what it does and why now, but only because
I was pointed to the thrift-to-cql document. The CQL
I am glad this document helped you.
I like to point to this 'thrift-to-cql' document, since it was really
useful to me when I found it, even if I had to read it at least 3 times
entirely and still need to refer to some piece of it sometimes because of
the complexity of what is explained in it.
Hi everyone,
I'm trying to wrap my head around Cassandra great ability to expand…
I have set up my first Cassandra node a while ago… it was working great, and
data wasn't so important back then.
Since I had a great experience with Cassandra I decided to migrate step by step
my MySQL data to
Hello,
I read in the docs that `nodetool repair` should be regularly run unless no
delete is ever performed. In my app, I never delete, but I heavily use the
ttl feature. Should repair still be run regularly? Also, does repair take
less time if it is run regularly? If not, is there a way to
Hi - We are struggling to understand how the counter family maintains
consistency in Cassandra.
Say Counter1 value is 1 and it is read by 2 clients at the same time who want
to update the value. After both write, it will become 3 ?
We observed the same behavior. During last repair the data distribution on
nodes was imbalanced as well resulting in one node bloating.
On Aug 1, 2013 12:36 PM, Carl Lerche m...@carllerche.com wrote:
Hello,
I read in the docs that `nodetool repair` should be regularly run unless
no delete is
Hi Carl,
The ‘repair’ is for data reads. Compaction will take care of the expired data.
The fact a repair runs long makes me think the nodes receive unbalanced amounts
of writes rather.
Regards,
Arthur
From: Carl Lerche
Sent: Thursday, August 01, 2013 12:35 PM
To: user@cassandra.apache.org
Hi Morgan,
The scaling out depends on several factors. The most intricate is perhaps
calculating the tokens.
Also the Cassandra version is important.
At this point in time I suggest you read section Adding Capacity to an
Existing Cluster at
Arthur,
Yes, my use case for this Cassandra cluster is analytics. I am building a
google dapper (application tracing) like system. I collect application
traces and write them to Cassandra. Then, I have periodic rollup tasks that
read the data, do some summarization and write it back.
Thoughts on
Hey folks,
Because 1.2.8 hasn't been pushed to the repo yet, I see that I can pick
up the package at http://people.apache.org/~eevans/ and install it
manually. This is great. I'm wondering though, is there a place where
I can pick up Debian packages for older releases? I definitely prefer
the
On 08/01/2013 12:27 PM, David McNelis wrote:
Hey folks,
Because 1.2.8 hasn't been pushed to the repo yet, I see that I can pick
up the package at http://people.apache.org/~eevans/ and install it
manually. This is great. I'm wondering though, is there a place where
I can pick up Debian
Thanks, fwiw, did I just blatantly miss some documentation saying those
existed there?
On Thu, Aug 1, 2013 at 3:32 PM, Blair Zajac bl...@orcaware.com wrote:
On 08/01/2013 12:27 PM, David McNelis wrote:
Hey folks,
Because 1.2.8 hasn't been pushed to the repo yet, I see that I can pick
up
Hello,
Say I have time series data for a table like this:
CREATE TABLE mytimeseries (
pk_part1 text,
partition bigint, e.g. partition per day or per hour
pk_part2 text, this is part of the partition key so I can
split write load
message_id timeuuid,
secondary_key1 text,
On Thu, Aug 1, 2013 at 12:49 PM, Gareth Collins
gareth.o.coll...@gmail.comwrote:
Would this be correct? Just making sure I understand how to best use
secondary indexes in Cassandra with time series data.
In general unless you ABSOLUTELY NEED the one unique feature of built-in
Secondary
I don't think they are listed from the cassandra.apache.org. BTW,
instructions are here:
http://www.datastax.com/documentation/cassandra/1.2/webhelp/index.html#cassandra/install/installDeb_t.html
Blair
On 08/01/2013 12:36 PM, David McNelis wrote:
Thanks, fwiw, did I just blatantly miss some
On Thu, Aug 1, 2013 at 12:26 PM, Robert Coli rc...@eventbrite.com wrote:
On Thu, Aug 1, 2013 at 9:35 AM, Carl Lerche m...@carllerche.com wrote:
I read in the docs that `nodetool repair` should be regularly run unless
no delete is ever performed. In my app, I never delete, but I heavily use
Cassandra is an excellent choice for write heavy applications.
Reading large sets of data is not as fast and not as easy, you may need to have
your client paging thru it and you may need slice queries and proper PK+Indexes
to think of in advance.
Regards,
Arthur
From: Carl Lerche
Sent:
TTL is effectively DELETE; you need to run a repair once every
gc_grace_seconds. If you don't, data might un-delete itself.
The undelete part is not true. btw: With CASSANDRA-4917 TTLed columns will
not even create a tombstone (assuming ttl gc_grace).
The rest of your mail I agree with :-)
Hi Arthur,
Thank you for your answer.
I have read the section Adding Capacity to an Existing Cluster prior to
posting my question.
Actually I was thinking I would like Cassandra choose by itself the token.
Since I want only some column family to be an ALL cluster, and other column
family to
On Thu, Aug 1, 2013 at 1:16 PM, Andrey Ilinykh ailin...@gmail.com wrote:
On Thu, Aug 1, 2013 at 12:26 PM, Robert Coli rc...@eventbrite.com wrote:
TTL is effectively DELETE; you need to run a repair once every
gc_grace_seconds. If you don't, data might un-delete itself.
How is it possible?
On 08/01/2013 01:16 PM, Andrey Ilinykh wrote:
TTL is effectively DELETE; you need to run a repair once every
gc_grace_seconds. If you don't, data might un-delete itself.
How is it possible? Every replica has TTL, so it when it expires every
replica has tombstone. I don't see how you
Hi Robert,
Can you shed some more light (or point towards some other resource) that
why you think built-in Secondary Indexes should not be used easily or
without much consideration? Thanks.
Regards,
Shahab
On Thu, Aug 1, 2013 at 3:53 PM, Robert Coli rc...@eventbrite.com wrote:
On Thu, Aug 1,
I recommend you do not add 1.2 nodes to a 1.1 cluster. We tried this, and
ran into many issues. Specifically, the data will not correctly stream
from the 1.1 nodes to the 1.2, and it will never bootstrap correctly.
On Thu, Aug 1, 2013 at 2:07 PM, Morgan Segalis msega...@gmail.com wrote:
Hi
On Thu, Aug 1, 2013 at 2:07 PM, Morgan Segalis msega...@gmail.com wrote:
Actually I was thinking I would like Cassandra choose by itself the token.
You NEVER want Cassandra to choose its own token in production. There is no
advantage to doing so and significant risk when used as a matter of
Hi Rob,
Le 2 août 2013 à 00:15, Robert Coli rc...@eventbrite.com a écrit :
On Thu, Aug 1, 2013 at 2:07 PM, Morgan Segalis msega...@gmail.com wrote:
Actually I was thinking I would like Cassandra choose by itself the token.
You NEVER want Cassandra to choose its own token in production.
On Thu, Aug 1, 2013 at 2:34 PM, Shahab Yunus shahab.yu...@gmail.com wrote:
Can you shed some more light (or point towards some other resource) that
why you think built-in Secondary Indexes should not be used easily or
without much consideration? Thanks.
1) Secondary indexes are more or less
Thanks a lot.
Regards,
Shahab
On Thu, Aug 1, 2013 at 8:32 PM, Robert Coli rc...@eventbrite.com wrote:
On Thu, Aug 1, 2013 at 2:34 PM, Shahab Yunus shahab.yu...@gmail.comwrote:
Can you shed some more light (or point towards some other resource) that
why you think built-in Secondary Indexes
28 matches
Mail list logo
