Re: [DISCUSS] List Apache Cassandra as a "company" on LinkedIn

I was unpleasantly surprised to find out that Linkedin group posts are not visible outside of the group, which greatly reduces post visibility. I originally supported the group creation because I thought the posts would be visible outside the group but this doesn't seem to be the case. The only th

[DISCUSS] List Apache Cassandra as a "company" on LinkedIn

I wanted to bring this up again from Benjamin's original thread . I agree with Melissa and I really think there's a lot of value in creating a company page on LinkedIn in addition to the "C* Community" group. There is a bigger potent

Re: [DISCUSS] Should we deprecate / freeze python dtests

> a well-defined path to reduce/eliminate code duplication and basic > documentation for newcomers to get up to speed with writing in-jvm dtests and > extending the framework Are python tests much better here? If not, I do not see why these should be blockers for their deprecation. Perfect fea

Re: [DISCUSS] Should we deprecate / freeze python dtests

I support deprecating python dtests, as long as in-jvm dtests have feature parity with python dtests, a well-defined path to reduce/eliminate code duplication and basic documentation for newcomers to get up to speed with writing in-jvm dtests and extending the framework. Em ter., 29 de mar. de 202

Re: [DISCUSS] Should we deprecate / freeze python dtests

It often does not work. I can attest to many wasted weeks, on some environments never getting them to work. They happen to work right now for me, though. I think the learning curve thing is a bit of a distraction, personally. I have always found python dtests hard to work with, both developing

Re: [DISCUSS] Should we deprecate / freeze python dtests

> In fact there is a high learning curve to setup cassandra-dtest environment I think this is fairly well documented: https://github.com/apache/cassandra-dtest/blob/trunk/README.md On Tue, Mar 29, 2022 at 5:27 PM Paulo Motta wrote: > > > I am curious about this comment. When I first joined I le

Re: [DISCUSS] Should we deprecate / freeze python dtests

> I am curious about this comment. When I first joined I learned jvm-dtest within an hour and started walking Repair code in a debugger (and this was way before the improvements that let us do things like nodetool)… python dtest took weeks to get working correctly (still having issues with the MBe

Re: [DISCUSS] Should we deprecate / freeze python dtests

One thing that we can add to docs is for people how to update the in-jvm framework and test their patches before asking for in-jvm api release. The assumption is those won’t be many updates needed I think, but it is good to be documented. On Tue, 29 Mar 2022 at 13:51, David Capwell wrote: > They

Re: [DISCUSS] Should we deprecate / freeze python dtests

> They use a separate implementation of instance initialization and thus they > test the test server rather than the real node. I think we can get rid of this by extending CassandraDaemon, just need to add a few hooks to mock out gossip/internode/client (for cases where the mocks are desired),

Re: [DISCUSS] Should we deprecate / freeze python dtests

> we should at least write extensive documentation on how to use/modify in-jvm > dtest framework before deprecating python dtests. We should have this for all our testing frameworks period, in-jvm dtest, python dtest, and ccm. They're woefully under-documented IMO. On Tue, Mar 29, 2022, at 6:11

Re: [DISCUSS] Should we deprecate / freeze python dtests

To elaborate a bit on the steep learning curve point, when mentoring new contributors on a couple of occasions I told them to "just write a python dtest" because we had no idea on how to test that functionality on in-jvm tests while the python dtest was fairly straightforward to implement (I can't

Re: [DISCUSS] Should we deprecate / freeze python dtests

> They use a separate implementation of instance initialization and thus they test the test server rather than the real node. I also have this concern. When adding a new service on CASSANDRA-16789 we had to explicitly modify the in-jvm dtest server to match the behavior from the actual server [1]

Re: [DISCUSS] Should we deprecate / freeze python dtests

> > They use a separate implementation of instance initialization and thus > they test the test server rather than the real node. This is actually my main concern. What is the real gap between the in-JVM tests server instance and a server as run by python DTests? Le mar. 29 mars 2022 à 00:08, be