Hey guys,
I'm having a problem with pig and cassandra and was hoping someone could
point me in the right direction. I've setup Pig and Cassandra and I'm able
to run through the example shown in the README.txt - I can view a list of
top column names. That's all good stuff.
What I would like to do
Hi All,
I have a query regarding the insert operation. The insert operation by default
inserts an new row or updates an existing row. Is it possible to prevent an
update but allow only inserts automatically ( especially when multiple clients
are writing to cassandra)? I was wondering if ther
i) Yes
ii) Well, so you don't actually want to use version 1 UUIDs for keys here.
Although
they mostly increase in byte order over time, it's only for the first 8
bytes. Instead,
you can use something like:
'timestamp-foo'
Where 'foo' might be a randomly generated string or something unique per
Tyler,
Thanks for answering my question. Can you please clarify on point (c)?
i] Are you saying that if I move to second row (identified by a rowKey in
Cassandra) after I hit 10 million col. values for 1st row, only then the
second row will be written to a new node in the cluster? meaning all th
On Fri, Oct 15, 2010 at 2:21 PM, Wayne wrote:
> The optimization definitely shaved off some time. Now it is running about 3x
> CFSTATS reported time. Below are the logs.
>
> There is a ~300ms time frame after the last ResponseVerbHandler prior to the
> resolver starting. Based on a quorum read the
FYI, The cassandra-ubuntu PPA has been updated to 0.6.6:
https://launchpad.net/~cassandra-ubuntu/+archive/stable
On Oct 14, 2010, at 11:57 AM, Eric Evans wrote:
>
> We've had plenty of Good Stuff[1] go into the 0.6 branch since the
> release of 0.6.5, so I'm pleased to announce the release of 0
sounds like https://issues.apache.org/jira/browse/CASSANDRA-1528 which
was fixed in 0.6.6.
On Fri, Oct 15, 2010 at 2:34 PM, Adam Holmberg
wrote:
> Greetings.
>
> I'm operating a several two-node clusters (version 0.6.5) on VMs in our
> development and test environments.
>
> After about a week of
Sounds good. You're right, CLI doesn't support this yet (but will shortly!)
On Fri, Oct 15, 2010 at 2:30 PM, J T wrote:
> Hmm, I don't have a java client that does all this. All of my stuff is in
> erlang using the thrift client.
> I can certainly raise a ticket and describe the problem though.
Greetings.
I'm operating a several two-node clusters (version 0.6.5) on VMs in our
development and test environments.
After about a week of operation under similar conditions, one of them
started throwing this:
WARN [main] 2010-10-12 08:08:31,245 CustomTThreadPoolServer.java (line 104)
Transport
Hmm, I don't have a java client that does all this. All of my stuff is in
erlang using the thrift client.
I can certainly raise a ticket and describe the problem though.
If the CLI supported querying by index I'd see if I could knock up an script
that did it but I don't think it does.
If you want
The optimization definitely shaved off some time. Now it is running about 3x
CFSTATS reported time. Below are the logs.
There is a ~300ms time frame after the last ResponseVerbHandler prior to the
resolver starting. Based on a quorum read the response resolver should kick
after 2 reads come in cor
a) 10 mil sounds fine. Just watch out for compaction. Huge rows can kill
you there,
from my understanding.
b) Use RandomPartitioner unless you absolutely have to use something else.
c) If you're inserting all along one row and only moving to another row when
you
hit 10 mil, you're only going to
I wrote some thoughts about this on my blog. I think it's still mostly correct:
* http://www.ayogo.com/techblog/2010/04/sorting-in-cassandra/
On Fri, Oct 15, 2010 at 11:14 AM, Wicked J wrote:
> Hi,
> I'm using TimeUUID/Sort by column name mechanism. The column value can
> contain text data (in
Hi,
I'm using TimeUUID/Sort by column name mechanism. The column value can
contain text data (in future they may contain image data as well) leading to
the possibility of a row out-growing the RAM capacity. Given this background
my questions are:
a] How many columns are recommended against one row
can you create a ticket with a test case?
On Fri, Oct 15, 2010 at 1:06 PM, J T wrote:
> Hi,
> If I do a secondary index look up with multiple index expressions (>1) that
> do not result in a match then I get a looping entry in the log until I
> terminate the cassandra server.
> e.g. (I'll use a
Hi,
If I do a secondary index look up with multiple index expressions (>1) that
do not result in a match then I get a looping entry in the log until I
terminate the cassandra server.
e.g. (I'll use a pseudo notation to indicate the examples)
lookup( [ { SecondaryIndexedColumnName, "ColumnValue
Aaron,
I updated the cassandra files and but still receive the same error (on
client side) with a different line number 551:
org.apache.thrift.TApplicationException: Internal error processing get_slice
at
org.apache.thrift.TApplicationException.read(TApplicationException.java:108)
at
org.apache.c
On Fri, Oct 15, 2010 at 10:59 AM, Eric Evans wrote:
> On Thu, 2010-10-14 at 13:07 -0700, Chris Oei wrote:
>> Also, once 0.7 is officially released, will 0.6 still be maintained
>> (sort of like Ubuntu's long-term releases), or will all 0.6
>> development stop?
>
> So far there hasn't been sufficie
On Thu, 2010-10-14 at 13:07 -0700, Chris Oei wrote:
> Also, once 0.7 is officially released, will 0.6 still be maintained
> (sort of like Ubuntu's long-term releases), or will all 0.6
> development stop?
Speaking with my Release Manager hat on, I would be willing to commit to
producing some addit
On Thu, Oct 14, 2010 at 7:36 PM, Henry Luo wrote:
> Thanks for the advice. Follow up questions:
>
> a) is 0.6.6 compactable with 0.6.1?
Yes, you can upgrade one node at a time and it will particpate w/ the
0.6.1 nodes until they are done too. Just restart w/ 0.6.6, no data
migration or commitlo
Upgrading from 0.6.5 to 0.6.6 is just a simple rolling restart on all
your nodes. Upgrading from 0.6 to 0.7 is a lot more work: you need to
change your code as the api changes and you need to shutdown the
entire cluster for upgrade.
I'm just about to upgrade my five node cluster to 0.6.6 and I'm
p
21 matches
Mail list logo
