Is there any plan to modularize cassandra codebase ? There are tons of subsystems within cassandra begging to be reused elsewhere. For instance, the implementation of gossip and countless other examples that could find life in other projects. -- -- Vladimir Vivien
Hello Everybody, In my use case we use Wide Rows whose columns are frequently updated, deleted and created. I was wondering if this case fits the Cassandra pattern and if there are any precautions to be taken. Kindly advice! Praveen
Hi, I am Apache Cassandra user and currently I am working on 3 nodes cluster in a single data center.I am using the random partitioner for data partitioner. Actually what I am trying to achieve is to have the range queries using Random partioner. I am stick and not getting any help to do it. I created my own column family using Column Familes as Indexes. It is written in page 14 of Apache Cassandra Documentation Book (April 17, 2012) by Datastax Although having the ability to do range scans on rows sounds like a desirable feature of ordered partitioners, there are ways to achieve the same functionality using column family indexes. Most applications can be designed with a data model that supports ordered queries as slices over a set of columns rather than range scans over a set of rows. I would like to know that how we can achieve the same functionality (Range Queries in Random Partitioner) using column family trick. Any simple example would be highly appreciated. Please email me back at ansark6 <at> hotmail.com Looking forward for your quick response. -Ansar
There is some data out of date, so we need compaction to delete it. When read, we should merge all the version to get full data, I think this will slow down the read performace. and at most time, we can avoid this. Then we can make compaction easy. Am I right? Thanks. zhangcheng
Hi, Cassandra CLI is the primary tool we use to view Cassandra Data. An Explorer has been developed to view data in a Cassandra Cluster. I thought that this would find convenient for the users to view data. This in the early stages and any feedback is highly appreciated. You can find a blog post on how to use it at [1] . [1] http://blog.shelan.org/2012/05/cassandra-explorer-gui-for-cassandra.html -- -- Shelan Perera Home: http://www.shelan.org Blog : http://www.shelanlk.com Twitter: shelan skype :shelan.perera gtalk :shelanrc I am the master of my fate: I am the captain of my soul. *invictus*
Hi Eric, I'm not sad anyway :) Having only types is not enough for the framework I'd like to implement client side. Prepare server side knows for sure what are the names of the parameters. Adding that to the parameters types will be perfect so. And I'm not asking for backport on v2. I do not mind targeting v3 and Cassandra 1.1+ only. I will open an improvement ticket to add parameters names to CqlPreparedResult then. Thanks ! - Pierre -----Original Message----- From: Eric Evans <eevans <at> acunu.com> Date: Sat, 12 May 2012 10:12:54 To: <dev <at> cassandra.apache.org> Reply-To: dev <at> cassandra.apache.org Subject: Re: CqlPreparedResult enhancements ? On Fri, May 11, 2012 at 4:37 PM, Pierre Chalamet <pierre <at> chalamet.net> wrote: > I hit some serious limitations with prepared statement in Cassandra 1.1. The > problem is CqlPreparedResult which brings no value for high level api > builders. > > For example, after prepare_cql_query on this query: >(Continue reading)
Hi,
I hit some serious limitations with prepared statement in Cassandra 1.1. The
problem is CqlPreparedResult which brings no value for high level api
builders.
For example, after prepare_cql_query on this query:
insert into People (firstname, lastname, birthyear) values (?, ?, ?)
I'd really like to discover the parameters names ('firstname', 'lastname'
and 'birthyear') with types if available from cf metadata if available.
For the moment, there is just nothing returned. Sad.
Knowing the names and types of the parameters could open a lot of
possibilities client side like a smart framework to feed parameters.
There is no problem with CqlResult since there is all the needed
informations.
Are there any plan to enhance prepared statements and specially
CqlPreparedResult ? In the current state, it's pretty limited and it's
impossible to create a great framework around prepared statement.
Thanks,
- Pierre
(Continue reading)
Hi, Let's say I want to use Cassandra's Git repository to build my own Cassandra .deb file which is _exactely_ the same as specified release (for example: cassandra-1.1) and apply there some patches of my choice. Could you please explain me how can I check which commit should I pick to do it properly? I think that there's an easy way to check it, but - unluckily - I don't know it (I'm not very familiar with git) or I miss something. I was expecting something like a tag or so, but I can't find anything that will make me sure that I found the commit I was looking for. Of course I can check tags, but they don't look like they are up-to-date... michal <at> aperture:~/workspace/cassandra-trunk$ git status # On branch cassandra-1.1 (...) michal <at> aperture:~/workspace/cassandra-trunk$ git describe cassandra-1.1.0-beta1-529-g8b81c8f (beta1?!) I know I can check debian/changelog for the last "New Release" message and then find/guess the appropriate commit basing on author, date/time and commit message, but I don't think it's the best approach ;) -- Kind regards, Michał(Continue reading)
See <https://builds.apache.org/job/Cassandra-quick/331/> ------------------------------------------ [...truncated 366 lines...] [junit] Testsuite: org.apache.cassandra.dht.ByteOrderedPartitionerTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.336 sec [junit] [junit] Testsuite: org.apache.cassandra.dht.CollatingOrderPreservingPartitionerTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.612 sec [junit] [junit] Testsuite: org.apache.cassandra.dht.OrderPreservingPartitionerTest [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1.398 sec [junit] [junit] Testsuite: org.apache.cassandra.dht.RandomPartitionerTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.947 sec [junit] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.641 sec [junit] [junit] Testsuite: org.apache.cassandra.gms.ArrivalWindowTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.6 sec [junit] [junit] Testsuite: org.apache.cassandra.gms.GossipDigestTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.058 sec [junit] [junit] Testsuite: org.apache.cassandra.gms.SerializationsTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 12.425 sec [junit] [junit] Testsuite: org.apache.cassandra.hadoop.ColumnFamilyInputFormatTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.208 sec(Continue reading)
See <https://builds.apache.org/job/Cassandra-quick/298/> ------------------------------------------ [...truncated 393 lines...] [junit] Testsuite: org.apache.cassandra.dht.ByteOrderedPartitionerTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.038 sec [junit] [junit] Testsuite: org.apache.cassandra.dht.CollatingOrderPreservingPartitionerTest [junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.281 sec [junit] [junit] Testsuite: org.apache.cassandra.dht.OrderPreservingPartitionerTest [junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.996 sec [junit] [junit] Testsuite: org.apache.cassandra.dht.RandomPartitionerTest [junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.802 sec [junit] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.474 sec [junit] [junit] Testsuite: org.apache.cassandra.gms.ArrivalWindowTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.453 sec [junit] [junit] Testsuite: org.apache.cassandra.gms.GossipDigestTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.042 sec [junit] [junit] Testsuite: org.apache.cassandra.gms.SerializationsTest [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 5.328 sec [junit] [junit] Testsuite: org.apache.cassandra.hadoop.ColumnFamilyInputFormatTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.222 sec(Continue reading)
RSS Feed369 | |
|---|---|
128 | |
114 | |
58 | |
151 | |
246 | |
254 | |
161 | |
173 | |
77 | |
97 | |
100 | |
214 | |
224 | |
222 | |
175 | |
239 | |
243 | |
133 | |
126 | |
118 | |
120 | |
117 | |
137 | |
127 | |
227 | |
142 | |
157 | |
134 | |
91 | |
150 | |
59 | |
99 | |
249 | |
53 |
