Re: Role of Hadoop code in Cassandra 5.0

I reached out to Hadoop Slack channel and I asked if there would be somebody to help us with the update. The first response was something about "why do you ask? we are not going to spend time on updating it for you" (fair enough), next responses were like "if this is so old and not maintained, i

Re: Role of Hadoop code in Cassandra 5.0

Regarding deprecation, while I support the deprecation and removal from the Cassandra codebase, I do think we should communicate that with the wider community (user thread?) so people aren't surprised - especially since it's already four months after the 4.1.0 release. That would hopefully also

Re: Role of Hadoop code in Cassandra 5.0

I think we already decided it in this thread. I was specifically asking this question: Deprecation would mean that the code has to be there whole 5.0 so we can remove it for real in 6.0? To which the response was: I think if we reach consensus here that decides it. I too vote to deprecate in 4

Re: Role of Hadoop code in Cassandra 5.0

Isn’t our deprecation rules that if we deprecate in 4.0.0 we can remove in 5.x, but 4.x needs to wait for 6.x? I am cool deprecating this and willing to pull into another repo if people (not me) are willing to maintain it (else just delete). > On Mar 10, 2023, at 1:13 AM, Jacek Lewandowski >

Re: [DISCUSS] New dependencies with Chronicle-Queue update

Deletion is the highest form of engineering ;) On Thu, Mar 16, 2023 at 7:09 AM Mick Semb Wever wrote: > > asm-analysis-9.4.jar > > asm-commons-9.4.jar > > asm-tree-9.4.jar > > asm-util-9.4.jar > > > FYI, on further inspection of the posix dependency, i've excluded > these four asm* dependenc

Re: [DISCUSS] Change the useage of nodetool tablehistograms

-1 on any change which breaks the previously documented usage. +1 any additions to what the tool can do without breaking previously documented behavior. > On Mar 16, 2023, at 7:42 AM, Josh McKenzie wrote: > > We could also consider augmenting the tool with new named arguments with the > functi

Re: [DISCUSS] New dependencies with Chronicle-Queue update

> asm-analysis-9.4.jar > asm-commons-9.4.jar > asm-tree-9.4.jar > asm-util-9.4.jar FYI, on further inspection of the posix dependency, i've excluded these four asm* dependencies.

Re: [DISCUSS] Change the useage of nodetool tablehistograms

We could also consider augmenting the tool with new named arguments with the functionality you described and leave the positional usage intact. On Thu, Mar 16, 2023, at 6:43 AM, Bowen Song via dev wrote: > The documented command options are: > >> nodetool tablehistograms [ | ] >> > > > That

Re: [EXTERNAL] Re: [DISCUSS] Next release date

Sorry, I realised that I hadn't included any completion date for CEP-7. At the current time we are looking at completion mid to end of April. Mike On Mon, 13 Mar 2023 at 11:34, Mike Adamson wrote: > CEP-7 Storage Attached Index is in review with ~430 files and ~70k LOC. > The bulk of the proje

Re: Should we cut some new releases?

OK. We can continue with 4.0.9, then 3.11.15, then 3.0.29 - in this order. From: Benjamin Lerer Sent: Thursday, March 16, 2023 11:43 To: dev@cassandra.apache.org Subject: Re: Should we cut some new releases? NetApp Security WARNING: This is an external em

Re: [DISCUSS] Change the useage of nodetool tablehistograms

The documented command options are: nodetool tablehistograms [ | ] That means one parameter will be treated as dot separated keyspace and table. Alternatively, two parameters will be treated as the keyspace and table respectively. To remain compatible with the documented behaviour, my s

Re: Should we cut some new releases?

> > Not sure about 4.0.9. We released 4.0.8 just few weeks ago. I would do > 4.1.1 first. It is true that there have not been many fixes since 4.0.8. Nevertheless CASSANDRA-18125 is a significant issue and 4.0 is certainly more used than 4.1

[DISCUSS] Change the useage of nodetool tablehistograms

Hello everyone : The nodetool tablehistograms have one argument which you can fill with only one table name with the format "keyspace_name.table_name /keyspace_name table_name", so that you can get the table histograms of the specied table. And if none arguments is set, all the tables' histograms

[VOTE] Release Apache Cassandra 4.1.1

Proposing the test build of Cassandra 4.1.1 for release. sha1: 8d91b469afd3fcafef7ef85c10c8acc11703ba2d Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.1-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1284/org/