The release vote is currently running, so, any time now. I believe the
original target release date was October 8th; but that fell on a weekend and
it's been delayed by a couple of regressions.
Regards,
Nick Telford
On 13 October 2011 14:24, Iroiso iro...@live.com wrote:
Hi all,
Can anyone
There are no plans to move to Maven for 2 reasons: 1) a majority of
committers favour Ant; 2) if it aint broke, don't fix it.
On 11 October 2011 03:33, Brian O'Neill b...@alumni.brown.edu wrote:
Will do. I've picked up where Gary left off. It is good starting point,
with a good mapping
set on deleting columns by timestamp, your best bet
is to build a Hadoop MapReduce job to do it for you. This will obviously be
quite a heavy-handed approach, so it's something you should not be running
very frequently.
Regards,
Nick Telford
On 28 September 2011 15:21, Samarth Gahire samarth.gah
It may be prudent to have someone to accept responsibility for each of the
official drivers in Extras. This way we could have a single ticket (perhaps
with sub-tickets for each driver) to ensure drivers are brought up to date
for each release.
This would be less about polluting the C* JIRA with
Yes, that's fine.
This is a question for the users@ list. The dev@ list is for development of
Cassandra itself.
Regards,
Nick Telford
On 28 July 2011 10:56, Eldad Yamin elda...@gmail.com wrote:
Hello,
Is it acceptable (in Cassandra terms) to get only 1 specific column?
I know that I can
Yes that's fine.
Also, this is a question for the users list. The dev list is for development
of Cassandra itself.
Regards,
Nick Telford
On 28 July 2011 10:56, Eldad Yamin elda...@gmail.com wrote:
Hello,
Is it acceptable (in Cassandra terms) to get only 1 specific column?
I know that I can
The timestamp of a column is an arbitrary version number, the value of which
is determined by the client that created the column. It's merely convention
(and convenience) that clients use the current timestamp. Since the
timestamp is a client-concern, and in non-trivial topologies Cassandra may
what you think. Would such an abstraction be useful? Is this something worth
pursuing?
--
Nick Telford
Peter's post, feel free to
tear them apart if you disagree. Just do it nicely.
Regards,
Nick Telford
On 31 March 2011 17:58, Peter Schuller peter.schul...@infidyne.com wrote:
In response to the apparent mass confusion about nodetool repair that
became evidence in the thread:
http://www.mail
...@rackspace.com wrote:
On Thu, 2011-03-31 at 18:57 +0100, Nick Telford wrote:
I don't think the Wiki is the right place for community maintained
user docs; it doesn't have the necessary structure.
The wiki is great at what wikis are great at, lowering the barrier to
contribution
list.
Regards,
Nick Telford
On 29 March 2011 10:34, Courtney Robinson sa...@live.co.uk wrote:
Okay, Dave Gardner, Nick Telford and myself met at the London Cassandra
meetup.
We were keen on getting a PHP CQL driver done and decided to use github
while working on it.
This mail is mainly
]: http://www.ibm.com/developerworks/java/library/j-nativememory-linux/
Cheers,
Nick Telford
architecture paper that describes the internal architecture used by
Cassandra.
Regards,
Nick Telford
On 24 January 2011 09:33, Zhijie Shen zjshe...@gmail.com wrote:
Oh, GSoC 2011 has started! I'm also interested in it:-)
There were a number of ideas proposed in the last year. I can see some of
them
The trade-off is in choosing which property you need: order preservation or
even load distribution.
The only reason a hybrid partitioner doesn't exist is that no one has been
able to create one. If you can create a partitioner that allows ordering
whilst ensuring an even load distribution, by all
Hi Maifi,
This is the expected behaviour for updating a value - the newest value
always wins in the event of a conflict (e.g. after two partitions converge).
Your use case is that of incrementing counters, which is not something that
is easily solved in Cassandra at the moment.
There are issues
15 matches
Mail list logo
