Re: [DISCUSS] Revisiting Java 11's experimental status

2020-08-19 Thread joshua . mckenzie
Should clarify - not saying automated tests are enough. Thinking we should articulate better what supported means (all tools work, etc - manually checking the swath of stuff that’s lacking automated testing assuming we even have a good idea of that scope). If we’re committing to all automated

Re: [DISCUSS] Revisiting Java 11's experimental status

2020-08-19 Thread Joshua McKenzie
> > This stance does not mean that java 11 testing is on-par with our > java 8 testing, it only means we treat reports of issues equality > regardless of JDK version. Outside our automated testing suites, what other testing as a project community do we consider necessary to dub something

Re: [DISCUSS] Revisiting Java 11's experimental status

2020-08-19 Thread J. D. Jordan
This makes sense to me. A bug is a bug regardless of the JVM that exposes it. Java 11 still considered experimental. Users should understand they are on the less trodden path when using it. -Jeremiah > On Aug 19, 2020, at 7:36 PM, David Capwell wrote: >

Re: Committing `CASSANDRA-13701 Lower default num_tokens` and the dtest slowdown…

2020-08-19 Thread Anthony Grasso
Hi Mick, No objections from me. It will be good to get this change into the 4.0 release. Whilst the slow down of the dtests is annoying, I am happy to see this change committed. As long as there are no regressions in the number of tests that pass then it should be fine. The proposal to raise a

Re: [DISCUSS] Revisiting Java 11's experimental status

2020-08-19 Thread David Capwell
> > s/ignore/defer until after 4.0 GA/g (semantic difference that may not sway > you) Even if it is experimental, I feel that it would be best for users if we treat java 11 bug reports the same as java 8 bug reports; it would be a bad user experience if a user found out we knew about an issue

Re: Feedback request on minor JMX interface incompatibility for CASSANDRA-15937

2020-08-19 Thread Jon Meredith
Thanks for the feedback, given three +1s and no objections then I'll move on to get it merged. I'm satisfied with the code and David Capwell has completed his review. If another contributor with more experience with how JMX is used in the community could look (particularly somebody with operator

Re: [DISCUSS] Revisiting Java 11's experimental status

2020-08-19 Thread Joshua McKenzie
> > java 11 is experimental, so lets ignore issue X s/ignore/defer until after 4.0 GA/g (semantic difference that may not sway you) If we block the release on JDK11 issues we find, it *seems* to me that that's the same as saying "JDK11 is supported" assuming we have the same a) level of testing

Re: [DISCUSS] Revisiting Java 11's experimental status

2020-08-19 Thread David Capwell
My statement was more coming from the fact that if we test on java 8 and find an issue it is a release blocker, so saying java 11 should be treated with the same regard as java 8 when it comes to filing/fixing issues; when it comes to filing and fixing issues, we shouldn't have different stances

Re: [DISCUSS] Revisiting Java 11's experimental status

2020-08-19 Thread Joshua McKenzie
> > 3) during 4.0 qualification, issues found on jdk 11 should block the > release Maybe we let 2 run and see how many issues there are before we call release blocking? On Tue, Aug 18, 2020 at 10:05 PM David Capwell wrote: > I would propose the following: > > 1) leave jdk 11 marked as

Committing `CASSANDRA-13701 Lower default num_tokens` and the dtest slowdown…

2020-08-19 Thread Mick Semb Wever
It was agreed¹ that 4.0 should have the new configuration defaults of num_tokens: 16 allocate_tokens_for_local_replication_factor: 3 13701's patches: against cassandra, cassandra-builds, cassandra-dtest, ccm; are reviewed, tested, and ready to commit. But the ccm and dtest patches required

Re: Cassandra Kubernetes SIG - status update

2020-08-19 Thread Cyril Scetbon
Hey Christopher, Okay cause I also need the same as I use Jolokia https://github.com/Orange-OpenSource/casskop/blob/master/docker/bootstrap/files/run.sh#L192-L199 Should I add it to the issue I

Re: [DISCUSS] CEP-7 Storage Attached Index

2020-08-19 Thread Jasonstack Zhao Yang
Hi Duy, great questions. > 1) SASI was pretty inefficient indexing wide partitions because the index > structure only retains the partition token, not the clustering colums. As > per design doc SAI has row id mapping to partition offset, can we hope that > indexing wide partition will be more