Any one here came across a situation like this ? Thank you!
On Thursday, July 9, 2015, Ajay Chander wrote:
> More information:
>
>
> Below is my cassandra bolt.
>
>
> public CassandraTest withCassandraBolt() {
>
> String[] rowKeyFields = {“item","location”};
>
> HashMap clientConfig = newHashMap
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.2.0-rc2.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of sourc
The Cassandra team is pleased to announce the release of Apache Cassandra
version 2.1.8.
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without compromising
performance.
http://cassandra.apache.org/
Downloads of source an
6 Binding +1, 2 non-binding +1, 1 non-binding -1 the vote passes
-- Forwarded message --
From: Jake Luciani
Date: Thu, Jul 9, 2015 at 9:04 AM
Subject: Re: [VOTE] Release Apache Cassandra 2.2.0-rc2
To: "dev@cassandra.apache.org"
We've discussed on https://issues.apache.org/jir
>
> It's up to the reviewer and author to transplant summaries of those
> conversations into JIRA (or GH were we to go that route). It is also a
> very real problem that we fall short on often.
Well, that's kind of my point: you have to exercise discretion here, just
as we have to exercise discre
(It's worth noting that the reason nits get miscategorized in the first
place is exactly because we lack comments explaining necessary subtleties)
On Thu, Jul 9, 2015 at 4:21 PM, Benedict Elliott Smith <
belliottsm...@datastax.com> wrote:
> It's up to the reviewer and author to transplant summari
Thus far there seems to be a large majority for the "Put the comments in
JIRA" approach.
Benedict - your comment concerning the arbitrary nature of what makes it
into JIRA is, I think, orthogonal to the choice of tool we use for the
review process from the perspective of IRC and offline chat. It's
I should clarify that I'm not at all proposing GH, but inline comments to
be retained (perhaps in modified form) alongside the code itself.
It's already arbitrary what makes it into JIRA, and what is just assumed to
be correct, or what is discussed on IRC, or offline. But even worse is that
this d
TL;DE I’m with Sylvain, Sam and Aleksey.
Having code related comments ”nearer“ to the code would be really nice, but
OTOH having ”everything“ in once place, namely JIRA, is much more important for
me.
I mean - where’s the border about what belongs to GH comments and what must be
in JIRA? Is it
With 6 Binding +1 and 2 non binding +1 and no -1 the vote passes.
-- Forwarded message --
From: Michael Shuler
Date: Wed, Jul 8, 2015 at 10:19 AM
Subject: Re: [VOTE] Release Apache Cassandra 2.1.8
To: dev@cassandra.apache.org
+1 non-binding
On 07/06/2015 12:04 PM, Jake Luciani
We've discussed on https://issues.apache.org/jira/browse/CASSANDRA-9749
This is technically a general issue with how we deal with CL errors and it
should be fixed in 2.1 branch as well as with new compressed CL in 2.2 so
it shouldn't block this vote.
On Wed, Jul 8, 2015 at 10:50 AM, Blake Eggle
I’m with Sylvain and Sam on this, as a person drinking from the JIRA firehose.
I’m fine with review happening on GH so long as it’s also mirrored on JIRA.
Someone could write a script that would automate this (take a PR, convert it to
a JIRA-formatted comment).
—
AY
On July 9, 2015 at 15:54:48
While that approach optimises for people paying close attention to the JIRA
firehose, it is less optimal for people trying to figure out after the fact
what is going on wrt certain tickets. Some of the more complex tickets I
cannot make head or tails of even when I was one of the main participants.
I'm +1 with Sylvain here; keeping the discussions open, accessible to all
and persistent seems more valuable than reducing the friction for
contributors & reviewers.
Personally, my workflow involves following the JIRA firehose, so I tend to
be aware (at least to some degree) of both "major" & "min
> One downside to that approach is that the extra barrier to entry makes it
> more of a 1-on-1 conversation rather than an open discussion via JIRA
> comments.
Yes, and I really worry about that. And I (see the "I", that's a totally
personal opinion) value keeping discussions as open as possible m
15 matches
Mail list logo
