Comments inline
>-Original Message-
>From: Jeff Jirsa [mailto:jji...@gmail.com]
>Sent: Sunday, February 18, 2018 10:58 PM
>To: u...@cassandra.apache.org
>Cc: dev@cassandra.apache.org
>Subject: Re: Cassandra Needs to Grow Up by Version Five!
>
>Comments inline
>
>
>> On Feb 18, 2018, at 9
the things you are asking for are unfortunately not tiny effort. as you don’t
seem to have the time to contribute code the best way you personally create
change would be (again) to file individual jiras for each enhancement or
feature request.
highlight key ones you filed via the mailing list t
html
There's a lot of things below I disagree with, but it's ok. I convinced
myself not to nit-pick every point.
https://issues.apache.org/jira/browse/CASSANDRA-13971 has some of Stefan's
work with cert management
Beyond that, I encourage you to do what Michael suggested: open JIRAs for
things you car
With 5 binding +1, 2 non-binding +1, and no other votes, this release
has passed. I will get 3.0.16 uploaded as soon as I can!
--
Kind regards,
Michael
On 02/14/2018 02:40 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.0.16.
>
> sha1: 890f319142ddd3cf2692ff45ff28
I count 6 binding +1, 1 non-binding +1, and no other votes for this
release of 3.11.2. I will get the artifacts uploaded shortly.
--
Kind regards,
Michael
On 02/14/2018 03:09 PM, Michael Shuler wrote:
> I propose the following artifacts for release as 3.11.2.
>
> sha1: 1d506f9d09c880ff2b2693e3e
Well said. Very fair. I wouldn’t mind hearing from others still. You’re a
good guy!
Kenneth Brotman
From: Jeff Jirsa [mailto:jji...@gmail.com]
Sent: Monday, February 19, 2018 9:10 AM
To: cassandra
Cc: Cassandra DEV
Subject: Re: Cassandra Needs to Grow Up by Version Five!
There's a
PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092)
--
The maximum expiration timestamp that can be represented by the storage
engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL
thatl expire after thi
PLEASE READ: MAXIMUM TTL EXPIRATION DATE NOTICE (CASSANDRA-14092)
--
The maximum expiration timestamp that can be represented by the storage
engine is 2038-01-19T03:14:06+00:00, which means that inserts with TTL
thatl expire after thi
Jeff, you helped me figure out what I was missing. It just took me a day to
digest what you wrote. I’m coming over from another type of engineering. I
didn’t know and it’s not really documented. Cassandra runs in a data center.
Now days that means the nodes are going to be in managed contai
10 matches
Mail list logo
