Using cassandra version 1.1.x and cql3?
-Vivek
On Fri, Oct 12, 2012 at 11:21 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
Thanks very much, Viktor! Is it something that is supported from CQL3?
If so, how can I create such column kind using CREATE TABLE?
Thierry
struct SuperColumn {
1: required binary name,
2: required listColumn columns,
}
Best regards / Pagarbiai
Viktor Jevdokimov
Senior Developer
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:
Hello!
I'm trying to get the column family type and I don't know why it's not
working.
I try to use the following code line:
Schema.instance.getColumnFamilyType(School, Grades);
This Keyspace and Column Family are inserted in Cassandra and this method
only returns null. If I try to get some
Hello!
is there any reason why Cassandra is shipped without mx4j-tools.jar ?
memory leaking ?
licensing issue ?
Cheers,
Ilya Shipitsin
I had a similar bug with 1.1.5 but I couldn't reproduce it so I didn't file a
bug. I did a rolling restart of my nodes and things went back to normal.
From: Manu Zhang owenzhang1...@gmail.commailto:owenzhang1...@gmail.com
Reply-To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
oh, forgot to mention that my Cassandra is 1.2beta-2
On Mon, Oct 15, 2012 at 11:11 PM, Michael Kjellman
mkjell...@barracuda.comwrote:
I had a similar bug with 1.1.5 but I couldn't reproduce it so I didn't
file a bug. I did a rolling restart of my nodes and things went back to
normal.
From:
Well I guess we will need some information to help you...
At least:
-Hardware ?
-Version of Cassandra ?
-Any specific action before restarting ?
-cassandra.yaml (options about compaction) ?
-...
Alain
2012/10/15 Manu Zhang owenzhang1...@gmail.com
My Cassandra is compacting like mad (look at
And to clarify my reply, this was a loop in compactions on
system-schema_columns specifically.
From: Michael Kjellman mkjell...@barracuda.commailto:mkjell...@barracuda.com
Reply-To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
I use default option for compaction:
in_memory_compaction_limit_in_mb: 64
multithreaded_compaction: false
compaction_throughput_mb_per_sec: 16
compaction_preheat_key_cache: true
I aborted Cassandra after a timeout query;
my Cassandra is 1.2beta-2
I don't what hardware information may
Thank you for the reply.
I am using the CQL 2.0 with Cassandra 1.1.5. The problem can be seen from
cqlsh too. The cqlsh commands are below, If CQL delete is executed with where
clause then it works. Hope this helps,
BTW, my environment is Windows 7, JDK 1.7, Cassandra 1.1.5, cqlsh using
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:
Hector provides load balancing so that requests can be distributed across
cluster nodes based on a specified policy, like round robin. Is there
anything similar planned for CQL? I see that there is an open issue (
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/issues/detail?id=41)
to
Sylvain - Getting a 404 still. I assume this is due to a delay in syncing
out to Apache content mirrors?
On 10/15/12 9:46 AM, Sylvain Lebresne sylv...@datastax.com wrote:
The Cassandra team is pleased to announce the release of Apache Cassandra
version 1.1.6.
Cassandra is a highly scalable
On Mon, Oct 15, 2012 at 7:24 PM, Michael Kjellman
mkjell...@barracuda.com wrote:
Sylvain - Getting a 404 still. I assume this is due to a delay in syncing
out to Apache content mirrors?
Yes, the apache mirrors can be rather long to sync. I usually send the
release email as soon as it is sync on
Hi all,
I have a 9-node cluster with a replication factor R=3. When I run repair
-pr on node-00, I see the exact same load and activity on node-{01,02}.
Specifically, compactionstats shows the same Validation tasks.
Does this mean that all 3 nodes will be repaired when nodetool returns? or
do I
Bootstrapping nodes do not handle reads requests until the bootstrap process is
complete.
JLewis
On Oct 13, 2012, at 11:19 PM, Andrey Ilinykh ailin...@gmail.com wrote:
Hello, everybody!
I'd like to clarify a bootstrapping process. As far as I understand,
bootstrapping node starts to accept
Hey,
we are writing a lot of data into a cassandra cluster for a batch loading
use case. We cannot use the sstable batch loader, so in order to speed up
the loading process we are using RF=1 while the data is loading. After the
load is complete, we want to increase the RF. For that, we are
Does it mean that during bootstrapping process only replicas serve
read requests for new node range? In other words, replication factor
is RF-1?
On Mon, Oct 15, 2012 at 12:20 PM, John Lewis lewili...@gmail.com wrote:
Bootstrapping nodes do not handle reads requests until the bootstrap process
+1Is this a consensus activity and is the master fixed, or does the voting
process migrate during the cycles??
On Oct 15, 2012, at 2:56 PM, Alexis Midon wrote:
Hi all,
I have a 9-node cluster with a replication factor R=3. When I run repair -pr
on node-00, I see the exact same
+1 It doesn't make sense that the xfr compactions are heavy unless they are
translating the file. This could be a protocol mismatch: however the
requirements for node level compaction and wire compaction I would expect to be
pretty different.
On Oct 15, 2012, at 4:42 PM, Matthias Broecheler
The Kafka team has resources for tuning the socket buffer sizes. It seems that
with a reasonable amount of memory, there should be an activity queue waiting
after the bootstrap process. Is this checked? Is it feasible to pick it up? Is
this already done?
On Oct 15, 2012, at 4:50 PM, Andrey
Only one region (node-00 is responsible for) will get repaired on all
three nodes.
Andrey
On Mon, Oct 15, 2012 at 11:56 AM, Alexis Midon alexismi...@gmail.com wrote:
Hi all,
I have a 9-node cluster with a replication factor R=3. When I run repair -pr
on node-00, I see the exact same load and
According to my experience if bootstrap is running on already Live cluster node
(and dead from sometime) then it start serving read during bootstrap process
also but if bootstrap is running on new node (which is joining cluster first
time) then read requests will not go to this node until
I see. So if I don't use the '-pr' option, triggering repair on node-00 is
sufficient to repair the first 3 nodes.
No need to cron a repair on node-{01,02}.
correct?
thanks for your answer.
On Mon, Oct 15, 2012 at 6:51 PM, Andrey Ilinykh ailin...@gmail.com wrote:
Only one region (node-00 is
forget it. this was nonsense.
On Mon, Oct 15, 2012 at 10:05 PM, Alexis Midon alexismi...@gmail.comwrote:
I see. So if I don't use the '-pr' option, triggering repair on node-00 is
sufficient to repair the first 3 nodes.
No need to cron a repair on node-{01,02}.
correct?
thanks for your
26 matches
Mail list logo
