Hi,
I am checking to see if we can include CASSANDRA-1448 in 4.0 release which
provides ZSTD compressor for Cassandra. Currently changes are under review,
implementation has unit test coverage similar to other compressors, also tested
in Instagram’s shadow clusters.
Implementation structure is
I agree with this. I generally am on the side of freedom and responsibility.
Limiting edits to certain fields turns people off. Something I want to very
much avoid if we can.
Dinesh
> On Dec 10, 2018, at 6:14 PM, Murukesh Mohanan
> wrote:
>
> On Tue, 11 Dec 2018 at 10:51, Benedict Elliott
On Tue, 11 Dec 2018 at 10:51, Benedict Elliott Smith
wrote:
>
> On 10 Dec 2018, at 16:21, Ariel Weisberg wrote:
> >
> > Hi,
> >
> > RE #1, does this mean if you submit a ticket and you are not a contributor
> > you can't modify any of the fields including description or adding/removing
> >
On 10 Dec 2018, at 16:21, Ariel Weisberg wrote:
>
> Hi,
>
> RE #1, does this mean if you submit a ticket and you are not a contributor
> you can't modify any of the fields including description or adding/removing
> attachments?
Attachment operations have their own permissions, like comments.
Hi,
RE #1, does this mean if you submit a ticket and you are not a contributor you
can't modify any of the fields including description or adding/removing
attachments?
RE #2, while bugs don't necessarily have a priority it's helpful to have it
sort logically with other issue types on that
New questions. This is the last round, before I call a proper vote on the
modified proposal (so we can take a mandate to Infra to modify our JIRA
workflows).
Thanks again to everyone following and contributing to this discussion. I’m
not sure any of these remaining questions are critical,
The “Impact” field idea sounds like a good potential follow-up discussion. I’d
prefer not to complicate this process when we’re seemingly nearing consensus,
particularly as I’m not personally sure what form such a field would take. But
it would be a relatively small modification, if you want
