On Wed, Oct 13, 2010 at 08:21, wrote:
> I want to create a thrift call and would like to know how to go about it.
>
> I think what I should do is this:
>
> - add my call to cassandra.thrift (eg. string test(1:required string arg),
> within 'service Cassandra')
>
> - run thrift -gen java cassandra
http://wiki.apache.org/cassandra/ThriftExamples is probably the place to start.
On Thu, Oct 14, 2010 at 08:57, wrote:
> Thank you, I used TFramedTransport as per your suggestion and it works now!
>
> Maybe I should write this up in the wiki? Could you suggest a suitable page?
>
> Alexander
>
>>
Yes, we should generate it in the right temp directory. That method
is an implementation of an interface method (FailureDetectorMBean),
meant to be invoked by JMX, which is why no other code calls it.
Gary.
On Wed, Oct 20, 2010 at 03:48, aaron morton wrote:
> I was reading through some code and
lable through JMX.
>
> A
> On 21 Oct 2010, at 01:55, Gary Dusbabek wrote:
>
>> Yes, we should generate it in the right temp directory. That method
>> is an implementation of an interface method (FailureDetectorMBean),
>> meant to be invoked by JMX, which is why no oth
On Wed, Oct 20, 2010 at 15:53, Aaron Morton wrote:
> I was helping a guy who in the end had a mixed beta1 and beta2
> cluster http://www.mail-archive.com/u...@cassandra.apache.org/msg06661.html
> I had a look around the code and have a couple of questions, just for my
> understanding.
> When ReadR
+1 beta3.
-1 on committing huge changes at the end of a cycle of betas. Let's
not do that any more.
Gary.
On Thu, Oct 28, 2010 at 05:48, Jonathan Ellis wrote:
> I vote for releasing the artifact as-is but as beta3. Broken HH is
> not something we should have in the final release but we need to
2010/10/29 Ted Zlatanov :
> On Thu, 28 Oct 2010 14:46:15 -0700 Chip Salzenberg wrote:
>
> CS> Short answer: "YES Please, but we will still want a side channel for
> CS> minimum overhead."
>
> 100% agreed on both counts. But IIRC the fastest side channel is to
> become a Cassandra node. Is that a
+1
On Thu, Oct 28, 2010 at 10:55, Eric Evans wrote:
>
> The RC1 vote[1] was vetoed due to, (among other things), the desire to
> see more testing after the somewhat disruptive changes made in
> CASSANDRA-1367[2]. Thus, I propose the follow artifacts for release as
> beta3.
>
> SVN:
> https://svn
A belated +1 as well.
On Thu, Nov 4, 2010 at 13:39, Eric Evans wrote:
>
> The list of changes[1] since 0.6.6 is fairly small, but there's been
> some interest in getting CASSANDRA-1656[2] (a HH bug) out to people. I
> propose the following for release as 0.6.7.
>
> SVN:
> https://svn.apache.org/
svn rev 917130
On Tue, Nov 9, 2010 at 13:48, Liangzhao Zeng wrote:
> Can anyone tell me what's thrift version using in Cassandra 0.66? I am using
> Mac os and trying to generate the java code from cassandra.thrift by
> myself.
>
>
> Cheers,
>
> Liangzhao
>
ckout.
Gary.
On Tue, Nov 9, 2010 at 15:15, Liangzhao Zeng wrote:
> Actually I can not find 917130 in http://svn.apache.org/repos/asf/thrift/,
> is there another svn rev?
>
> Cheers,
> Liangzhao
>
> On Tue, Nov 9, 2010 at 2:59 PM, Gary Dusbabek wrote:
>>
>> svn rev
+1
On Thu, Nov 11, 2010 at 17:39, Eric Evans wrote:
>
> A regression caused by CASSANDRA-1622[1] (and fixed in CASSANDRA-1727[2])
> made its way into the last release. With that fixed now (along with an
> 11th hour backport of CASSANDRA-1722[3]), I propose the following
> artifacts for 0.6.8.
>
>
+1
On Sat, Nov 20, 2010 at 11:41, Eric Evans wrote:
>
> Barring anything unforeseen, we should be just about there. I propose
> the following for release as 0.7.0 RC1.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-...@r1037265
> 0.7.0-rc1 artifacts: http://people.apach
We develop the cassandra database. I believe it is currently beyond
the scope of this project to advocate for and against third party
client libraries. If it isn't, then we should be actively developing
client libraries.
I think that to take it upon ourselves to do this advocating as a
project i
+1. I say go for it.
On Sat, Dec 4, 2010 at 11:27, Peter Schuller
wrote:
> Without weighing in on the remainder of the discussion; regardless of
> what happens what do people think about at least making some minor
> structural changes to e.g. the wiki? For example, putting the Thrift
> API in a s
+1
On Mon, Dec 6, 2010 at 12:25, Eric Evans wrote:
>
> There have been quite a few changes[1] since the release of RC1, too
> many to not seek wider testing. I propose the following for release as
> 0.7.0 RC2.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-...@r1042731
I've seen one or two instances of bit-rot in the avro CassandraServer,
and I suspect there are probably others. It doesn't get first-class
testing status, so I suspect it will be buggy unless it gets more
usage by others.
One other aspect is there is a fair amount of code baggage that needs
to be
+1 on the RC. +1 on the 24hr vote.
On Thu, Dec 30, 2010 at 14:08, Eric Evans wrote:
>
> It looked like RC3 would be the last before a stable release, we were
> looking so good, but a couple of deal-breakers[1] cropped up recently.
> I propose the following artifacts for release as 0.7.0-rc4.
>
>
Stephen,
Please lay down some mvn/ant wisdom on us... Is there a way to
link/include the dependency logic from the 'pom' target and the
ivy.xml file we use? It would be great if the dependency information
could be consolidated in one place.
Great work, btw.
Gary.
On Sun, Jan 2, 2011 at 14:50,
+1. I didn't test the artifacts, but any effort to get mvn artifacts
published that doesn't force mvn on the entire project gets my vote.
Gary.
On Sun, Jan 2, 2011 at 14:50, Stephen Connolly
wrote:
> As I am not a cassandra committer I'd rather do the promotion with a vote.
> There are two stag
Voted and moved this discussion to a different thread.
My goal (other devs please chime in because I'm interested) would be
to still rely on ant for building and generating a pom, without the
requirement to explicitly install maven. If we could get rid of
ivy.xml by having the relevant details in
+1
On Thu, Jan 6, 2011 at 11:17, Eric Evans wrote:
>
> RC 4 seems to be holding up OK, shall we? I propose the following for
> release as 0.7.0 (aka "For Reals Yo").
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0@r1055934
> 0.7.0 artifacts: http://people.apache.or
The old thing still starts up. +1.
On Tue, Jan 4, 2011 at 11:51, Eric Evans wrote:
>
> Feels about time for a new 6.x point release; Lots of interesting
> changes have landed since the last release. I propose the following for
> release as 0.6.9.
>
> SVN:
> https://svn.apache.org/repos/asf/cass
On Tue, Jan 11, 2011 at 12:49, Peter Schuller
wrote:
> I have noticed API06 and API07 being created. API being de-synched
> with API07 now.
>
> Should we just make API not contain anything and all, and simply link
> to the appropriate page for each version?
^ I like that idea. Make it a landing
It wouldn't be hard to do. Cassandra is structured in such a way that
it is pretty easy to wrap a transport around a few classes that handle
most of the client interaction. Last September I created a
RESTful-like version of Cassandra in just a few hours. I haven't
maintained the branch, but you
u very much for the information. BTW, It seems that your transport
> code is not in the Cassandra's trunk. Is it going add that code into the
> trunk? BTW, do you think what I suggested would be worth? If so, I would
> like to implement it.
>
> Thanks,
>
> Indika
>
> On
On Mon, Jan 17, 2011 at 11:12, Jake Luciani wrote:
> Hi,
>
> I'd to discuss if/when we should be using Avro or any serialization tool in
> the Cassandra core.
>
> Some context: We have begun the process of removing Avro from the service
> layer CASSANDRA-926. We currently use Avro for schema migra
doh!
+1.
On Wed, Jan 19, 2011 at 13:40, Eric Evans wrote:
>
> We should probably get the fix for CASSANDRA-1959 out to users of 0.6.
> I propose the following artifacts for release as 0.6.10.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.6@r1060906
> 0.6.10 artifacts
+1
On Thu, Jan 27, 2011 at 12:18, Eric Evans wrote:
>
> CASSANDRA-2058[1] is serious enough to warrant a new 0.6 point release.
> I propose the following for release as 0.6.11.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.6@r1064231
> 0.6.11 artifacts: http://people.
+1
On Jan 28, 2011 1:07 PM, "Stephen Connolly"
wrote:
Since there does not seem to be any desire to accept CASSANDRA-1997
Can the PMC vote to approve the use of the Cassandra mark by the
mojo.codehaus.org project for the Cassandra Maven Plugin
+1 Approve
0 don't care
-1 Veto
72 hours
PMC vot
I've been uncomfortable with the amount of features I perceive are
going into our maintenance releases for a while now. I thought it
would stop after we committed ourselves to having a more predictable
major release schedule. But getting 0.7.1 out feels like it's taken a
lot more effort than it s
+1
On Thu, Feb 10, 2011 at 11:52, Eric Evans wrote:
>
> I propose the following for release as 0.7.1.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1069461
> 0.7.1 artifacts: http://people.apache.org/~eevans
>
> The vote will be open for 72 hours.
>
> [1]: http://g
+1
On Tue, Feb 15, 2011 at 15:57, Eric Evans wrote:
>
> CASSANDRA-2165[1] is troublesome enough to warrant a new release. I
> propose the following for 0.7.2.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.2@r1071063
> 0.7.2 artifacts: http://people.apache.org/~eeva
+1
On Thu, Feb 17, 2011 at 16:20, Eric Evans wrote:
>
> Sorry folks, cut-and-paste errors.
>
> On Thu, 2011-02-17 at 15:57 -0600, Eric Evans wrote:
>> SVN:
>> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7.2@r1071063
>
> That should be:
> https://svn.apache.org/repos/asf/cassan
Duplicates CASSANDRA-2258.
On Wed, Mar 9, 2011 at 06:15, Stephen Connolly
wrote:
> Hmm failure due to some difference when the code is instrumented... points
> to some threading issue that might need to be looked at.
>
> In any case, in order to get Code Coverage to work consistently, it would be
+1
On Mar 11, 2011 6:47 PM, "Eric Evans" wrote:
>
> It's that time again. I propose the following for release as 0.7.4.
> What say you?
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1080811
> 0.7.4 artifacts: http://people.apache.org/~eevans
>
> The vote will be ope
Everybody is right. The CQL<->SQL naming ambiguity is a problem. We
need to do something about this before it gets out of hand.
I've been thinking about alternatives all weekend. Here's one thing I
came up with that I think will do nicely.
Using our thrift API (the *old* way of doing things) h
Hi everybody. You may need to reconfigure your IDE's the next time
you update. I upgraded trunk to use thrift 0.6 last night.
Cheers,
Gary.
+1
On Mon, Apr 18, 2011 at 13:44, Eric Evans wrote:
>
> OK. Here are artifacts for a proposed 0.8 beta1 release.
>
> You will note the addition of three new artifacts, cql-1.0.0.tar.gz,
> txcql-1.0.0.tar.gz and apache-cassandra-cql-1.0.0.jar. These are
> language drivers for CQL; Be sure to inc
+1
On Tue, Apr 19, 2011 at 20:35, Eric Evans wrote:
>
> Let's try this again. I propose the following artifacts for release as
> 0.8.0 beta1.
>
> You will note the addition of three new artifacts, cql-1.0.0.tar.gz,
> txcql-1.0.0.tar.gz and apache-cassandra-cql-1.0.0.jar. These are
> language dr
+1
On Fri, Apr 22, 2011 at 12:17, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 0.7.5.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-113/org/
+1
On Mon, May 2, 2011 at 20:36, Eric Evans wrote:
>
> I propose the following artifacts for release as 0.8.0 beta2.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1098882
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-011
> Dri
+1
On May 12, 2011 7:14 PM, "Eric Evans" wrote:
>
> OK, let's try this again; I propose the following artifacts for release
> as 0.8.0 RC1.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8@r1102510
> Artifacts:
> https://repository.apache.org/content/repositories/orgap
+1
On Fri, May 13, 2011 at 04:39, Sylvain Lebresne wrote:
> It's been only a little more than 2 weeks since the release of 0.7.5, but
> since then we have corrected a handfull of fairly important bugs, incuding:
> https://issues.apache.org/jira/browse/CASSANDRA-2554
> https://issues.apache.org/
+1
On Thu, May 19, 2011 at 12:42, Sylvain Lebresne wrote:
> Release 0.7.6 shipped with a bug in the debian packaging that prevent the
> package from being correctly set up (CASSANDRA-2481). Since the debian
> packaging is in-tree, I'm not sure we have better choice than doing a new
> release.
>
>
+1. Let's ship this thing already.
On Mon, May 30, 2011 at 14:04, Eric Evans wrote:
> OK, let's try this yet again; I propose the following artifacts for release
> as 0.8.0 (final).
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8.0@r1129278
> Artifacts:
> https://r
On Tue, Jun 7, 2011 at 03:08, Eric Evans wrote:
>
> Sylvain and I have been discussing release issues while here at
> buzzwords, and some of the issues are related to drivers. Not
> surprising since that's a new concept for us, and there wasn't much
> thought given to the current organization.
>
That problem is already solved externally. I don't see the value of
reimplementing it inside of cassandra.
Gary.
On Fri, Jun 17, 2011 at 09:58, Tim Wisniewski wrote:
> Hi,
>
> My understanding is data corruption can occur if the node clocks are too far
> out of sync. What if Cassandra nodes ma
On Mon, Jun 20, 2011 at 09:45, Sylvain Lebresne wrote:
> On Mon, Jun 20, 2011 at 1:58 PM, Shotaro Kamio wrote:
>> Hi,
>>
>> NEWS.txt claims that rolling upgrade works.
>> Upgrading
>> -
>> - 0.8.1 is backwards compatible with 0.8, upgrade can be achieved by a
>> simpl
On Mon, Jun 20, 2011 at 10:12, Sylvain Lebresne wrote:
> Yes, there has been a change of the messaging server version
> between 0.8.0 and 0.8.1.
>
Do we hate our users or something? This is a bad idea.
The whole idea behind CASSANDRA-1015 was that we would reserve changes
like this to major ver
After discussion on #cassandra-dev, I amend my vote to -0.
On Mon, Jun 20, 2011 at 10:29, Gary Dusbabek wrote:
> On Mon, Jun 20, 2011 at 10:12, Sylvain Lebresne wrote:
>> Yes, there has been a change of the messaging server version
>> between 0.8.0 and 0.8.1.
>>
>
&
+1
On Fri, Jun 24, 2011 at 16:03, Sylvain Lebresne wrote:
> Alright, third time's not always the charm, my mistake. Let's try again.
> I propose the following artifacts for release as 0.8.1:
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8.1@r1139326
> Artifacts:
> h
Following @cassandra on twitter or a google alert would be simple enough I
think.
Gary.
On Mon, Jul 18, 2011 at 14:26, Nick Bailey wrote:
> What do we think about having a separate mailing list for just
> cassandra related announcements. The main purpose being announcing new
> releases once the
On Wed, Aug 24, 2011 at 17:22, Eric Evans wrote:
> There's been discussion happening in #2761
> (https://issues.apache.org/jira/browse/CASSANDRA-2761) on and off now
> for more than 3 months, and I think it could benefit from some wider
> exposure.
>
> The issue was created in the wake of the driv
+1
On Wed, Aug 31, 2011 at 15:57, Eric Evans wrote:
> If at first you don't succeed[3], try, try again; I propose the
> following for release as 0.7.9.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1163795
> Debian Package Artifacts: http://people.apache.org/~eeva
+1
On Wed, Sep 14, 2011 at 10:56, Sylvain Lebresne wrote:
> It's been a week since the freeze and we don't have too many open tickets for
> 1.0.0. It seems like a good time to get the first beta out. Note that this is
> not a release candidate yet, so the goal is more to get some wider testing, t
+1
On Thu, Sep 15, 2011 at 11:16, Sylvain Lebresne wrote:
> A few bug causing annoyance on the upgrade path have been fixed since 0.8.5,
> as
> well as a few other improvements, so I propose the following artifacts
> for release
> as 0.8.6.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/
+1
On Sat, Oct 8, 2011 at 06:39, Sylvain Lebresne wrote:
> We've all been waiting for it. Apache Cassandra 1.0 is getting real folks.
> All (known) blocking issues have been resolved and October 8th is there, I see
> no reason to delay this any longer. I propose the following artifacts for
> rele
+1
On Mon, Oct 10, 2011 at 11:24, Sylvain Lebresne wrote:
> As said while closing previous vote, CASSANDRA-3338 felt important enough to
> warrant a reroll. So here it is: I propose the following artifacts for release
> as 1.0.0 (those are the same as the previous + the patch for CASSANDRA-3338
>
It turns out that it is pretty easy (or it was a year ago) to replace
the native Cassandra transport with your own. I wrote about it on my
blog (http://www.onemanclapping.org/2010/09/restful-cassandra.html),
using REST as an example.
On Mon, Oct 10, 2011 at 20:12, Brian O'Neill wrote:
> My team
+1
On Oct 11, 2011 10:27 AM, "Sylvain Lebresne" wrote:
> Let's hope third times will be the charm. With #3343, #3345 and #3346 in, I
> propose the following artifacts for release as 1.0.0.
>
> SVN:
> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-1.0.0@r1181820
> Artifacts:
> https
On Tue, Nov 15, 2011 at 17:23, Jonathan Ellis wrote:
> I started a "users survey" thread over on the users list (replies are
> still trickling in), but as useful as that is, I'd like to get
> feedback that is more quantitative and with a broader base. This will
> let us prioritize our development
+1
On Nov 29, 2011 1:28 PM, "Sylvain Lebresne" wrote:
> So 1.0.4 was actually pretty catastrophic. CASSANDRA-3540 is a clear
> blocker
> and CASSANDRA-3539 is critical too. For now, we've pulled the plug on
> 1.0.4 by
> removing it from the website (and I broke the debian upgrade to 1.0.4),
> bu
+1
On Mon, Nov 28, 2011 at 11:09, Sylvain Lebresne wrote:
> I'ts been some time since we have a 0.8 release and the changelog is getting
> fairly big. There's no reason to hold all those goodies from users.
> I thus propose the following artifacts for release as 0.8.8.
>
> SVN:
> https://svn.apa
+1
On Sat, Dec 10, 2011 at 19:26, Sylvain Lebresne wrote:
> I know, I know, 1.0.5 is just out the oven. Yet, we've fixed a number of
> annoying bugs, and in particular CASSANDRA-3551 and CASSANDRA-3577,3585
> probably justify a new release by themselves. I thus propose the following
> artifactfs
+1
On Sat, Dec 10, 2011 at 20:10, Sylvain Lebresne wrote:
> A second vote in the same day!? I know what you've just though: santa comes
> early this year. But no, you're not dreaming: CASSANDRA-3472 (0.8.8)
> re-enabled cross-DC efficient writes that was mistakenly disabled since pretty
> much f
I'd like to see the clients stay as simple as possible, keeping the
bind parameters as strings.
Not all languages Javascript make it easy to do binary.
Gary.
On Wed, Jan 11, 2012 at 15:14, Eric Evans wrote:
> On Wed, Dec 14, 2011 at 5:49 PM, Eric Evans wrote:
>> Thanks to the hard work of Ric
Hi everybody,
When first starting work on the CQL driver for node[1] , work was done
on github. After a while it was moved to apache-extras so it could be
more uniform with the other drivers. However, the experience on
apache-extras is not good as collaboration is difficult.
That, and because t
( it only has
> CQL drivers). this name convention is very popular for noders & will make
> module consistent to be get searched on npm.
>
> On Wed, Feb 1, 2012 at 12:48 AM, Kelley Reynolds <
> kelley.reyno...@rubyscale.com> wrote:
>
>> On Tue, Jan 31, 2012 at 9:12 A
+1
On Wed, Feb 22, 2012 at 08:57, Sylvain Lebresne wrote:
> Been some time since 1.0.7 and bugs have been fixed, I thus propose the
> following artifacts for release as 1.0.8.
>
> sha1: fe6980eb7d2df6cb53fd8a83226f91789beaced8
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=sho
+1
On Fri, Apr 20, 2012 at 12:38, Sylvain Lebresne wrote:
> The RC1 went well and we basically don't have any issue open left, so I
> think it's time to release the final Cassandra 1.1. I thus propose the
> following artifacts for release as 1.1.0.
>
> sha1: c671532825b9e05bd2b50e3aa2d1c5f5156d1c
201 - 271 of 271 matches
Mail list logo
