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 wrote:
> Hi all,
>
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 wrote:
> Will do. I've picked up where Gary left off. It is good starting point,
> with a good mapping between REST and get/set
wiki.apache.org/cassandra/Counters) we should probably
replace those with the appropriate CQL wherever applicable.
Regards,
Nick Telford
On 6 October 2011 12:29, aaron morton wrote:
> With 1.0 almost here I was going to try and spruce up the wiki a bit to
> make things a little more we
list.
If you have your heart 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 201
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 im
Connection pooling is a client concern, are you referring to a particular
CQL driver or high-level client? If so, which one?
On 25 August 2011 13:07, Vivek Mishra wrote:
> Any plan for connection pooling? is it already in place?
>
> -Vivek
>
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 wrote:
> Hello,
> Is it acceptable (in Cassandra terms) to get only 1 specific column?
> I know that I
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 wrote:
> Hello,
> Is it acceptable (in Cassandra terms) to get only 1 specific column?
> I know that I can g
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
not
to discussion among the various client devs to see
what you think. Would such an abstraction be useful? Is this something worth
pursuing?
--
Nick Telford
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
>
some ideas I had while reading 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 wrote:
> In response to the apparent mass confusion about nodetool repair that
> became evidence in the threa
er than add to the noise on the dev list.
Regards,
Nick Telford
On 29 March 2011 10:34, Courtney Robinson 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 wor
int me in the right
direction.
[1]: http://www.ibm.com/developerworks/java/library/j-nativememory-linux/
Cheers,
Nick Telford
#x27;s an application
architecture paper that describes the internal architecture used by
Cassandra.
Regards,
Nick Telford
On 24 January 2011 09:33, Zhijie Shen wrote:
> Oh, GSoC 2011 has started! I'm also interested in it:-)
>
> There were a number of ideas proposed in the last year. I ca
t's just a mirror of the Riptano docs. In order to indicate that the
release is ready for the general public we need to have the resources
readily available to help them figure out what Cassandra is and how to use
Cassandra properly.
To summarise: +0.5
Regards,
Nick Telford
On 13 January
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 issue
18 matches
Mail list logo
