One other question: Has anyone considered taking a crack at modifying
the CqlPagingRecordReader to use the DataStax java driver? I am not
sure how that kind of cross-pollination of different projects works,
but I thought the paging mechanisms in the DataStax driver might help
simplify the CqlPagin
+1
On Wed, Feb 5, 2014 at 10:50 AM, Sylvain Lebresne wrote:
> As said while closing the previous vote, we needed to re-roll for
> CASSANDRA-6648, so I propose the following artifacts for release as 2.0.5.
> I also propose an expedited 24h vote.
>
> sha1: 29670eb6692f239a3e9b0db05f2d5a1b5d4eb8b0
+1
On Wed, Feb 5, 2014 at 2:23 AM, Sylvain Lebresne wrote:
> We just released 1.2.14 but unfortunately it shipped with a relatively
> serious
> regression: https://issues.apache.org/jira/browse/CASSANDRA-6648. That
> regression has been fixed, but we need to get that fix to users, so I
> propose
+1
On Wed, Feb 5, 2014 at 3:50 AM, Sylvain Lebresne wrote:
> As said while closing the previous vote, we needed to re-roll for
> CASSANDRA-6648, so I propose the following artifacts for release as 2.0.5.
> I also propose an expedited 24h vote.
>
> sha1: 29670eb6692f239a3e9b0db05f2d5a1b5d4eb8b0
>
+1
On Feb 5, 2014 2:24 AM, "Sylvain Lebresne" wrote:
> We just released 1.2.14 but unfortunately it shipped with a relatively
> serious
> regression: https://issues.apache.org/jira/browse/CASSANDRA-6648. That
> regression has been fixed, but we need to get that fix to users, so I
> propose
> the
+1
On Feb 5, 2014 2:24 AM, "Sylvain Lebresne" wrote:
> We just released 1.2.14 but unfortunately it shipped with a relatively
> serious
> regression: https://issues.apache.org/jira/browse/CASSANDRA-6648. That
> regression has been fixed, but we need to get that fix to users, so I
> propose
> the
+1
On Feb 5, 2014 3:50 AM, "Sylvain Lebresne" wrote:
> As said while closing the previous vote, we needed to re-roll for
> CASSANDRA-6648, so I propose the following artifacts for release as 2.0.5.
> I also propose an expedited 24h vote.
>
> sha1: 29670eb6692f239a3e9b0db05f2d5a1b5d4eb8b0
> Git:
>
As said while closing the previous vote, we needed to re-roll for
CASSANDRA-6648, so I propose the following artifacts for release as 2.0.5.
I also propose an expedited 24h vote.
sha1: 29670eb6692f239a3e9b0db05f2d5a1b5d4eb8b0
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h
+1
On Wed, Feb 5, 2014 at 9:23 AM, Sylvain Lebresne wrote:
> We just released 1.2.14 but unfortunately it shipped with a relatively
> serious
> regression: https://issues.apache.org/jira/browse/CASSANDRA-6648. That
> regression has been fixed, but we need to get that fix to users, so I
> propose
We just released 1.2.14 but unfortunately it shipped with a relatively
serious
regression: https://issues.apache.org/jira/browse/CASSANDRA-6648. That
regression has been fixed, but we need to get that fix to users, so I
propose
the following artifacts for release as 1.2.15. As there has been little
We were almost there but unfortunately
https://issues.apache.org/jira/browse/CASSANDRA-6648 is a regression, an
not a minor one, so I'm closing that vote and will restart a third "strike"
shortly. Sorry about that. I'll keep the re-roll short however, 24h, many
bugs have been fixed since 2.0.4 and
11 matches
Mail list logo
