On Tue, Dec 17, 2013 at 7:43 AM, Michael Kjellman
wrote:
> I¹ve also seen behavior where prepared statements are lost during a
> rolling restart..haven¹t had a chance to debug/git bisect yet. Anyone else
> seen anything similar?
>
I'd be somewhat surprised if someone hasn't. We don't persists pre
I¹ve also seen behavior where prepared statements are lost during a
rolling restart..haven¹t had a chance to debug/git bisect yet. Anyone else
seen anything similar?
On 12/16/13, 10:40 PM, "Sylvain Lebresne" wrote:
>Alright, this vote is thus close. I'll re-roll when we've made sure we
>fixed al
Alright, this vote is thus close. I'll re-roll when we've made sure we
fixed all the regressions so we'll see when that is.
--
Sylvain
On Tue, Dec 17, 2013 at 1:01 AM, Brandon Williams wrote:
> Or rather: https://issues.apache.org/jira/browse/CASSANDRA-6493
>
> I would still prefer a 24h vote
You've been added (or will be once this page loads)
On Mon, Dec 16, 2013 at 6:46 PM, Dan Rollo wrote:
> Hi,
>
> The Cassandra Wiki says to request access on this list to edit the wiki. I
> found a minor typo, and would like to post a correction.
>
> Thanks,
> Dan
>
> (wiki id: bhamail)
>
>
>
Hi,
The Cassandra Wiki says to request access on this list to edit the wiki. I
found a minor typo, and would like to post a correction.
Thanks,
Dan
(wiki id: bhamail)
Or rather: https://issues.apache.org/jira/browse/CASSANDRA-6493
I would still prefer a 24h vote after resolution though.
On Mon, Dec 16, 2013 at 5:56 PM, Brandon Williams wrote:
> Changing to -1 as https://issues.apache.org/jira/browse/CASSANDRA-6488seems
> to be a real problem.
>
>
> On Mon,
Changing to -1 as
https://issues.apache.org/jira/browse/CASSANDRA-6488seems to be a real
problem.
On Mon, Dec 16, 2013 at 12:12 PM, Brandon Williams wrote:
> +1
>
>
> On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne wrote:
>
>> So now that CASSANDRA-6485 has been committed, I propose the follo
+1
On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne wrote:
> So now that CASSANDRA-6485 has been committed, I propose the following
> artifacts for release as 1.2.13.
>
> sha1: 4be9e6720d9f94a83aa42153c3e71ae1e557d2d9
> Git:
>
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;
+1
On Mon, Dec 16, 2013 at 3:38 AM, Sylvain Lebresne wrote:
> So now that CASSANDRA-6485 has been committed, I propose the following
> artifacts for release as 1.2.13.
>
> sha1: 4be9e6720d9f94a83aa42153c3e71ae1e557d2d9
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=r
So now that CASSANDRA-6485 has been committed, I propose the following
artifacts for release as 1.2.13.
sha1: 4be9e6720d9f94a83aa42153c3e71ae1e557d2d9
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.2.13-tentative
Artifacts:
https://repository.apache.org/conten
10 matches
Mail list logo