Bertrand,
Thank you very much for reaching out.
I put the following in the upcoming board report, but I'll repeat it
here because I think it sums things up:
"If nothing else, it's clear we all care very deeply about having
successful open source software projects."
To that end, let's all move fo
+1
On Wed, Nov 9, 2016 at 9:09 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.10.
>
> sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
> Artifacts:
> https://reposit
+1
On Wed, Nov 9, 2016 at 9:08 AM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.10.
>
> sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative
> Artifacts:
> https://rep
I propose the following artifacts for release as 3.10.
sha1: 072b5271a88328b909b230d0e30df1c7476fdb3f
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1133/org/apache/c
I propose the following artifacts for release as 3.0.10.
sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.10-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1132/org/apac
Michael, thanks for the info. It sounds to me a very serious performance
regression. :(
On Tue, Nov 8, 2016 at 11:39 AM, Michael Kjellman <
mkjell...@internalcircle.com> wrote:
> Yes, We hit this as well. We have a internal patch that I wrote to mostly
> revert the behavior back to ByteBuffers wi
Yes, We hit this as well. We have a internal patch that I wrote to mostly
revert the behavior back to ByteBuffers with as small amount of code change as
possible. Performance of our build is now even with 2.0.x and we've also
forward ported it to 3.x (although the 3.x patch was even more complic
This is very expensive:
"MessagingService-Incoming-/2401:db00:21:1029:face:0:9:0" prio=10
tid=0x7f2fd57e1800 nid=0x1cc510 runnable [0x7f2b971b]
java.lang.Thread.State: RUNNABLE
at
org.apache.cassandra.db.marshal.IntegerType.compare(IntegerType.java:29)
at
org.apache.
+1 (non-binding)
On Tue, 8 Nov 2016 at 10:05 Jake Farrell wrote:
> +1
>
> -Jake
>
> On Mon, Nov 7, 2016 at 12:11 AM, Jeff Jirsa wrote:
>
> > There exists a nearly unused mailing list,
> client-...@cassandra.apache.org
> > [0].
> >
> > This is a summary of the email threads over the past 12 mont
+1
-Jake
On Mon, Nov 7, 2016 at 12:11 AM, Jeff Jirsa wrote:
> There exists a nearly unused mailing list, client-...@cassandra.apache.org
> [0].
>
> This is a summary of the email threads over the past 12 months on that
> list:
>
> 1) ApacheCon Seville CFP Close notice
> 2) Datastax .NET driver
Dear Cassandra PMC and community,
The Board of Directors of the ASF apologizes for contributing to the
sometimes heated nature of discussions in the last few days on this
list.
We have reminded board members to remain civil in such discussions,
whatever the context and history.
As published in t
On 07/11/2016 10:52, Benedict Elliott Smith wrote:
> Hi Mark,
>
> Thanks, that was a calm and diplomatic email.
>
> recognise where they might need to apologise
>
>
> I will start the ball rolling here, as I have not always been generous in
> my interpretations of others' actions, and have cert
12 matches
Mail list logo
