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
Hi,
I'm attempting to build an index on a column acting as part of a composite
key.
This is what I have so far:
CREATE TABLE userinfo2 (
campaignId int,
TS timestamp,
somevalue text,
PRIMARY KEY (campaignId, TS)
);
INSERT INTO userinfo2 (campaignId, TS,
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
OK,
A different question then, Is there any meaning of discussing composite key
not in the context of a table primary key ?
For making additional hierarchy inside a single row by using columns.
On Mon, Nov 5, 2012 at 12:14 PM, Sylvain Lebresne sylv...@datastax.comwrote:
On Mon, Nov 5, 2012 at
Hi ,
I am using cpp thrift client to manipulate data in cassandra.
I am unable to get the timestamp from a keyslice result.
Any ideas ?
The following is piece of my code to get column names and values from the
result.
cass.set_keyspace(myks3);
string key = myrk3;
I just figured it out ...
returnstrg \: results[i].columns[x].column.timestampstd::endl;
From: Hagos, A.S. [a.s.ha...@tue.nl]
Sent: Monday, November 05, 2012 1:37 PM
To: user@cassandra.apache.org
Subject: how to get timestamp from slicerange result
Hi
- ... 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
use to have a ticket for that (can't find it back with a quick search
but JIRA search suck and I didn't bother
Rule of thumb is to try to keep nodes under 400GB.
Compactions/Repairs/Move operations etc become a nightmare otherwise. How
much data do you expect to have on each node? Also depends on caches,
bloom filters etc
On 11/5/12 8:57 AM, Oleg Dulin oleg.du...@gmail.com wrote:
I have 4 nodes at my
Our compactions/repairs have already become nightmares and we have not
approached the levels of data you describe here (~200 GB). Have any
pointers/case studies for optimizing this?
On Nov 5, 2012, at 12:00 PM, Michael Kjellman wrote:
Rule of thumb is to try to keep nodes under 400GB.
Should be all under 400Gig on each.
My question is -- is there additional overhead with replicas making
requests to one another for keys they don't have ? how much of an
overhead is that ?
On 2012-11-05 17:00:37 +, Michael Kjellman said:
Rule of thumb is to try to keep nodes under
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
Hello!
I was wondering if someone could help me a bit with triggers in cassandra.
I am doing a school project with this DBMS, and i would be very happy if
you could send me a simple example/explanation of a trigger.
Thank you!! :)
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
You will have one extra hop. Not big deal, actually. And many client
libraries (astyanax for example) are token aware, so they are smart
enough to call the right node.
On Mon, Nov 5, 2012 at 9:12 AM, Oleg Dulin oleg.du...@gmail.com wrote:
Should be all under 400Gig on each.
My question is --
Hey Guys,
What should I look out for when deploying a single node installation? We want
to launch a product that uses Cassandra and since we are going to have very
little load initially, we were thinking of just going live with one node and
eventually add more nodes as the load (hopefully)
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.
On Mon, Nov 5, 2012 at 12:24 PM, Sylvain Lebresne sylv...@datastax.com wrote:
On Mon, Nov 5, 2012 at 4:12 PM, Edward Capriolo
There are no built-in trigger. Someone has written an aspect oriented
piece to do triggers outside of the project.
http://brianoneill.blogspot.com/2012/03/cassandra-triggers-for-indexing-and.html
On Mon, Nov 5, 2012 at 12:30 PM, davuk...@veleri.hr wrote:
Hello!
I was wondering if someone
On Mon, Nov 5, 2012 at 12:49 PM, Drew Kutcharian d...@venarc.com wrote:
Hey Guys,
What should I look out for when deploying a single node installation? We want
to launch a product that uses Cassandra and since we are going to have very
little load initially, we were thinking of just going
Oh, ok. Thank you for info.!
There are no built-in trigger. Someone has written an aspect oriented
piece to do triggers outside of the project.
http://brianoneill.blogspot.com/2012/03/cassandra-triggers-for-indexing-and.html
On Mon, Nov 5, 2012 at 12:30 PM, davuk...@veleri.hr wrote:
Should be fine if one node can deal with your read and write load.
Switching from SimpleStrategy to RackAware can be a pain. That¹s a
potential growth point way down the line (if you ever have your nodes on
different switches). You might want to just setup your keyspace as
RackAware if you intend
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
Hello,
I have a Cassandra ring with 4 nodes in 0.8.9 and like to upgrade all nodes to
1.1.5.
It would be great that the upgrade has no downtime or minimal downtime of the
ring.
After I brought down one of the nodes and upgraded it to 1.1.5, when I tried to
bring it up,
the new 1.1.5 node
Do a rolling upgrade of the ring to 1.0.12 first and then upgrade to 1.1.x.
After each rolling upgrade, you should probably do the recommend nodetool
upgradesstables, etc. The datastax documentation about upgrading might be
helpful for you: http://www.datastax.com/docs/1.1/install/upgrading
I did have a tombstone. I couldn't seem to delete it, so I truncated the column
family.
Thanks for the help.
Steve
[default@system] list HintsColumnFamily;
Using default limit of 100
Using default column limit of 100
---
RowKey: 5554
I wasn't able
I understand that with one node we will have no HA, but since we are just
starting out we wanted to see what would be the bare minimum to go to
production with and as we see traction we can add more nodes.
Switching from SimpleStrategy to RackAware can be a pain.
Can you elaborate a bit? What
A remark like maybe we just shouldn't allow that and leave that to the
map-reduce side would make sense, but I don't see how this is misleading.
Yes. Bingo.
It is misleading because it is not useful in any other context besides
someone playing around with a ten row table in cqlsh. CQL stops me
As the OP of this thread, it is a big itch for my use case. Repair ends up
streaming tens of gigabytes of data which has expired TTL and has been
compacted away on some nodes but not yet on others. The wasted work is not
nice plus it drives up the memory usage (for bloom filters, indexes, etc)
On Mon, Nov 5, 2012 at 12:23 PM, Drew Kutcharian d...@venarc.com wrote:
Switching from SimpleStrategy to RackAware can be a pain.
Can you elaborate a bit? What would be the pain point?
If you don't maintain the same replica placement vis a vis nodes on
your cluster, you have to dump and
I don't think that is possible in Cassandra.
Others please correct me if I am wrong.
Thanks and Regards
Rishabh
-Original Message-
From: davuk...@veleri.hr [mailto:davuk...@veleri.hr]
Sent: Monday, November 05, 2012 11:00 PM
To: user@cassandra.apache.org
Subject: triggers(newbie)
Hello,
I am using cfstats of nodetool I have following doubts:
1) What is the difference between size (live) and size (total)
2) Number of keys in column family is 100 but cfstats shoes 128. (Tried
compaction, cleanup and scrub but same result ).
Kindly help
Thanks and Regards
Ok, I slightly misunderstood your initial complain, my bad. I largely agree
with you, though I'm more conflicted on what the right resolution is. But
I'll follow up on the ticket to avoid repetition.
On Mon, Nov 5, 2012 at 10:42 PM, Edward Capriolo edlinuxg...@gmail.comwrote:
I created
31 matches
Mail list logo
