Re: [VOTE] Release Apache Cassandra 5.0-alpha1

+1 nb.I think it’s good to get an alpha out there for people to starting trying out the features which are done.On Aug 25, 2023, at 4:03 PM, Mick Semb Wever wrote:There was lazy consensus on this thread: https://lists.apache.org/thread/mzj3dq8b7mzf60k6mkby88b9n9ywmsgw  and also the announcement

Re: [VOTE] Release Apache Cassandra 5.0-alpha1

There was lazy consensus on this thread: https://lists.apache.org/thread/mzj3dq8b7mzf60k6mkby88b9n9ywmsgw and also the announcement about the staged release was out for a longer period of time to raise objections. Not that it's too late to object, just that it's been raised for attention twice

New episode of The Apache Cassandra (R) Corner podcast!

Link to the next episode (video): https://drive.google.com/file/d/1nu_h8JczmAI59GhnDunTI9Oew-TxmzNU/view?usp=sharing s2e8 - Otavio Santana (You may have to download it to play) It will remain in staging for 72 hours, going live (assuming no objections) by Monday, August 28th. If anyone should

Jira: Project logo with incorrect/no trademark

Hello: The Cassandra logos on the ASF Project Logos page are outdated, as they include lowercase letters and no trademark. This Jira request includes logos to be replaced on the site, which requires a committer to publish: https://issues.apache.org/jira/browse/CASSANDRA-18621 The logo on the

Re: [Discuss] Enabling JMX in in-jvm dtests (by default)

Great. So, we are going to remove legacy solution / mocking of JMX, nodetool will interact only via a proper JMX connection and a developer is required to enable JMX feature to be able to execute nodetool commands. If JMX feature is not present an exception is thrown saying it has to be enabled

Re: [VOTE] Release Apache Cassandra 5.0-alpha1

I concur. Those are major features... From: C. Scott Andreas Sent: Friday, August 25, 2023 9:06 AM To: dev@cassandra.apache.org Subject: [EXTERNAL] Re: [VOTE] Release Apache Cassandra 5.0-alpha1 You don't often get email from sc...@paradoxica.net. Learn why this

Re: [DISCUSSION] Dependency management in our first alpha release

Thank you all. We are going to continue with those tickets and related problems then. On Maxim's question: "Do we need a separate issue for 'org.caffinitas.ohc:ohc-core-j8' or we should handle everything under [2]?" It depends on whether someone has the time to sit and deal with the complete

Re: [VOTE] Release Apache Cassandra 5.0-alpha1

A snapshot artifact seems more appropriate for early testing to me, rather than a voted / released build issued by the project given how much has yet to land.- ScottOn Aug 25, 2023, at 8:46 AM, Ekaterina Dimitrova wrote:+1On Fri, 25 Aug 2023 at 11:14, Mick Semb Wever

Re: [DISCUSSION] Shall we remove ant javadoc task?

To close this one. The patch to fix javadoc and enable in CI under the ant check the failure under broken javadoc is ready. After considering the current project status, we decided to delay committing it until 5.0 is feature complete and all bug CEPs are in. Best regards, Ekaterina On Mon, 21

Re: [VOTE] Release Apache Cassandra 5.0-alpha1

+1 On Fri, 25 Aug 2023 at 11:14, Mick Semb Wever wrote: > > Proposing the test build of Cassandra 5.0-alpha1 for release. > > DISCLAIMER, this alpha release does not contain the expected 5.0 > features: Vector Search (CEP-30), Transactional Cluster Metadata > (CEP-21) and Accord Transactions

Re: [VOTE] Release Apache Cassandra 5.0-alpha1

Given the disclaimer, can you just confirm why we'd cut an alpha now - we're trying to lock protocols and give other people an integration target, presumably? On Fri, Aug 25, 2023 at 8:14 AM Mick Semb Wever wrote: > > Proposing the test build of Cassandra 5.0-alpha1 for release. > >

[VOTE] Release Apache Cassandra 5.0-alpha1

Proposing the test build of Cassandra 5.0-alpha1 for release. DISCLAIMER, this alpha release does not contain the expected 5.0 features: Vector Search (CEP-30), Transactional Cluster Metadata (CEP-21) and Accord Transactions (CEP-15). These features will land in a later alpha release. Please

Re: [Discuss] Enabling JMX in in-jvm dtests (by default)

I’d agree that anywhere we’re calling `nodetoolResult` or `nodetool` in a test, it would be better to enable JMX and use it rather than the older mocks we set up to enable calling the mbeans directly. I don’t think enabling JMX by default is the right way to go mostly due to the added

Re: [Discuss] Enabling JMX in in-jvm dtests (by default)

I would prefer to have one standard way to do it, and given the options I would prefer it be proper JMX instead of mocking. Kind Regards, Brandon On Fri, Aug 25, 2023 at 4:20 AM Miklosovic, Stefan wrote: > > Hi list, > > I want to gather a feedback for this comment (1). > > Long story short,

[Discuss] Enabling JMX in in-jvm dtests (by default)

Hi list, I want to gather a feedback for this comment (1). Long story short, until JMX feature was introduced, we kind of hacked / mocked the calls to MBeans from IInstance, like this (2). If you notice, there is a lot of methods throwing UnsupportedOperationException because we had no proper