Re: Immediately Deprecated Code

For offline upgrades, we are aiming to maintain all compatibility. > > Take care when removing code, there are various (serdes) classes that look > like they are for other components but are also used in the storage engine. > > > > On Tue, 31 Oct 2023 at 18:42, Claude Warren, J

Re: Immediately Deprecated Code

t;> logic was triggered. >> >> (1) >> https://github.com/apache/cassandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L97-L108 >> >> >> From: Claude Warren, Jr via dev >&g

Immediately Deprecated Code

I was thinking about code that is used to migrate from one version to another. For example the code that rewrote the order of the hash values used for Bloom filters. That code was necessary for the version it was coded in. But the next version does not need that code because the next version is

Re: Immediately Deprecated Code

sandra/blob/trunk/test/distributed/org/apache/cassandra/distributed/upgrade/UpgradeTestBase.java#L97-L108 > > ________________ > From: Claude Warren, Jr via dev > Sent: Tuesday, October 31, 2023 10:57 > To: dev > Cc: Claude Warren, Jr > Subject: Immediatel

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

e, easy scale up / > down, etc, and always-ZCS for non-object store deployments. > > Jon > > On 2023/09/25 06:48:06 "Claude Warren, Jr via dev" wrote: > > I have just filed CEP-36 [1] to allow for keyspace/table storage outside > of > > the standard storage s

Re: CASSANDRA-18775 (Cassandra supported OSs)

I closed 18775 as it did not seem reasonable after discussions here. I have been working on 16565 and have a pull request [1] and an experimental suite to show the differences. [2] [1] https://github.com/apache/cassandra/pull/2842 [2] https://github.com/Aiven-Labs/compare_oshi_sigar On Wed,

Re: CASSANDRA-16565

I ended up posting the code at https://github.com/Aiven-Labs/compare_oshi_sigar if anyone wants to take a look and see if they get differing results on various systems. On Tue, Oct 24, 2023 at 4:59 PM Brandon Williams wrote: > On Tue, Oct 24, 2023 at 7:48 AM Claude Warren, Jr via dev >

Development Dependencies documentation.

I just had to change dependencies in Cassandra for the first time and I think the documentation [1] is out of date. First I think most of the file edits are in the ".build" directory. Adding jars to the "lib" directory works until calling "ant realclean", so perhaps the instructions should

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

gt;>> >>>>>> Jake >>>>>> >>>>>> On Tue, Sep 26, 2023 at 12:56 PM Benedict >>>>>> wrote: >>>>>> > >>>>>> > I agree with Ariel, the more suitable insertion point is probabl

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

> show up above the `ChannelProxy` layer that will depend on the backend. > > > > Ideally there would be some config to specify several backend > filesystems and their individual configuration that can be used, as well as > configuration and support for a "backen

multiple ParameterizedClass objects?

I have a case where I would like to be able to specify a collection of ParameterizedClass objects in the configuration file. Is there a standard way to do this? If not, does anyone have a suggestion for a clean way to implement it? Claude

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

tate, and not an implementation >> detail of one part of the final state? >> >> >> >> >> >> >> On Sun, Sep 24, 2023 at 11:49 PM Claude Warren, Jr via dev < >> dev@cassandra.apache.org> wrote: >> >>> I have just filed CEP-36

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

perately needs, especially if one of those tiers is >>>> some sort of object storage >>>> - This looks like it's a foundational piece that enables that. Perhaps >>>> by a team that's already implemented this end to end? >>>> - Rather than b

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

t; filesystems and their individual configuration that can be used, as well as > configuration and support for a "backend file router" for file creation > (and opening) that can be used to route files to the backend most > appropriate. > > > > Regards, > >

[DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

I have just filed CEP-36 [1] to allow for keyspace/table storage outside of the standard storage space. There are two desires driving this change: 1. The ability to temporarily move some keyspaces/tables to storage outside the normal directory tree to other disk so that compaction can

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

de, SSD, HDD, and data placement based > on requests. After briefly browsing the proposals, it seems that there are > some differences. Can you help to do some explain ？ Thanks 。 > > > Claude Warren, Jr via dev 于2023年9月25日周一 > 14:49写道： > >> I have just filed CEP-3

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

>> Fileystems). There will probably also be backend specific behaviors that >> show up above the `ChannelProxy` layer that will depend on the backend. >> > >> > Ideally there would be some config to specify several backend >> filesystems and their individual configurat

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

gt;>> > Support for multiple storage backends including remote storage >>>> backends is a pretty high value piece of functionality. I am happy to see >>>> there is interest in that. >>>> > >>>> > I think that `ChannelProxyFactory` as an in

Re: [DISCUSS] CEP-36: A Configurable ChannelProxy to alias external storage locations

gt; backends. We need to be able to list files and really the full range of >>> filesystem interactions that Java supports should work with any backend to >>> make development, testing, and using existing code straightforward. >>> > >>> > It's a little mo

Re: [DISCUSS] CommitLog default disk access mode

I think introducing the feature is a good idea. I also think that it should _NOT_ be enabled by default for all the reasons stated above. Finding a cohort of users who are interested in turning it on would provide a nice testbed to shake out any issues without affecting everyone. On Tue, Oct 17,

CASSANDRA-18775 (Cassandra supported OSs)

I am looking at https://issues.apache.org/jira/browse/CASSANDRA-18775 and want to ensure that I do not remove too many libraries. I think that preserving any sigar library where the file name contains the word "linux" or "macosx" should be acceptable. This will preserve: libsigar-amd64-linux.so

CASSANDRA-16565

I am working on https://issues.apache.org/jira/browse/CASSANDRA-16565 and have a small testing program that executes the sigar and equivalent OSHI methods to verify that they are the same. I would like to have this run on various platforms. I have tgz with all the libraries and code as well as a

Fixes for UDF NPE during restart.

CASSANDRA-18739 describes a reproducible NPE on restart with some UDFs. The solution outlined in that ticket was not used and a much simpler solution provided by Stefan Miklosovic was implemented. There are 2 pull requests open for Cassandra 4.0 and 4.1 that have the fairly simple fix as well as

review request for pull 1741

Greetings, Can I get a review of https://github.com/apache/cassandra/pull/1741 other than the obvious issue with CHANGES.txt does anyone see anyting that needs to be fixed?

Re: [DISCUSS] CEP-20: Dynamic Data Masking

I am more interested in the motivation where it is stated: Many users have the need of masking sensitive data, such as contact info, > age, gender, credit card numbers, etc. Dynamic data masking (DDM) allows to > obscure sensitive information while still allowing access to the masked > columns,

Re: [DISCUSS] CEP-20: Dynamic Data Masking

The PCI DSS Standard v4_0 requires that credit card numbers stored on the system must be "rendered unreadable", thus this proposal is _NOT_ a good way to protect credit card numbers. In fact, for any critically

Re: [DISCUSS] CEP-20: Dynamic Data Masking

This seems to me to be a client display filter, applied at the last moment as data are streaming back to the client. It has no impact on any keys, queries or secondary internal index or materialized view. It simply prevents the display from showing the complete value. It does not preclude

Re: [DISCUSS] CEP-20: Dynamic Data Masking

This change appears to be looking at two aspects: 1. Add metadata to columns 2. Add functionality based on the metadata. If the system had a generic user defined metadata and the ability to define filter functions at the point where data are being returned to the client it would be

Re: [DISCUSS] CEP-21: Transactional Cluster Metadata

Should (**) It may seem counterintuitive, that A is being written to even after > we've stopped reading from it. This is done in order to guarantee that by > the time we stop writing to the node giving up the range, there is no > coordinator that may attempt reading from it without learning about

Re: [Proposal] add pull request template

Since there seems to be agreement, I opened a ticket (CASSANDRA-17837) and a pull request (https://github.com/apache/cassandra/pull/1799) in so that the final text can be hashed out and accepted. I also used the proposed pull request in the text of the pull so that it can be seen in all its glory

Is this an MV bug?

# Table definitions Table [ Primary key ] other data base [ A B C ] D E MV[ D C ] A B E # Initial data base -> MV [ a b c ] d e -> [d c] a b e [ a' b c ] d e -> [d c] a' b e ## Mutations -> expected outcome M1: base [ a b c ] d e' -> MV [ d c ] a b e' M2: base [ a b c ] d'

Re: Is this an MV bug?

ate, no? > > > On Fri, Aug 19, 2022 at 10:17 AM Benedict wrote: > >> If M1 and M2 both operate over the same partition key they won’t be >> separate mutations, they should be combined into a single mutation before >> submission to SP.mutate >> >> > On 19 Aug 20

Re: Is this an MV bug?

SP.mutate > > > On 19 Aug 2022, at 10:05, Claude Warren, Jr via dev < > dev@cassandra.apache.org> wrote: > > > >  > > > > # Table definitions > > > > Table [ Primary key ] other data > > base [ A B C ] D E > > MV[ D C ] A B E >

CEP-21 and complete cluster replacement.

After CEP-21 would it be possible to take a cluster of 6 nodes, spin up 6 new nodes to duplicate the 6 existing nodes and then spin down the original 6 nodes. Basically, I am thinking of the case where a cluster is running version x.y.z and want to run x.y.z+1, can they spin up an equal number of

CEP-23: Enhancement for Sparse Data Serialization

I would like to discard CEP-23. As I am the proposer, is a vote required? What is the process? Claude

Re: CEP-23: Enhancement for Sparse Data Serialization

> gone to a vote and/or a vote has passed. > > If someone else wants to pick it up later that's fine. > > On Tue, Oct 25, 2022, at 7:35 AM, Claude Warren, Jr via dev wrote: > > I would like to discard CEP-23. As I am the proposer, is a vote required? > > What is the process? > > Claude > > >

[DISCUSS] WIP pull request for CASSANDRA-17773

Greetings, I have created a pull request [1] as a work in progress for CASSANDRA-17773. The idea here is to move the boiler plate include of cassandra.in.sh and cassandra-env.sh into one sourced script that also provides a function (verify_env) to verify that required variables are set.

Re: CEP-21 and complete cluster replacement.

will make the bootstrapping (and decommissioning) > experience a whole lot more stable and predictable, so in the short term I > would expect the recommended rolling approach to upgrades would improve > significantly. > > > > On 20 Oct 2022, at 12:24, Claude Warren, Jr via dev < >

Re: [Discuss] CEP-24 Password validation and generation

dingly. As of now, observers / subscribers are meant to integrate with >> JMX through which these events flow. >> >> Do you think Diagnostics events would satisfy your needs? >> >> Regards >> >> >> From: Claude Wa

Fwd: [Discuss] CEP-24 Password validation and generation

I managed not to send this to the mailaing list... I don't know the govt spec. but there is a US govt security level where you are not allowed to inform the user why the login failed. It seems to me that there are 2 intertwined components being discussed. 1) A component to perform a user

Re: [Discuss] CEP-24 Password validation and generation

aries. This might be included in > the CEP but I would keep it out for the very first implementation and it > can be finished afterwards in some other commit. I do not find it > absolutely necessary to do it right now. > > Regards, > > Stefan > >

Re: [Discuss] CEP-24 Password validation and generation

can go just so > far when it comes to prevent people from doing wrong things, maybe > increasing the password history to 20 last passwords would be enough. > Anyway, I plan to make this historical password verification optional so it > might be turned on / off on demand. > > Fin

Re: [Discuss] CEP-24 Password validation and generation

tics events would satisfy your needs? > > Regards > > ________________ > From: Claude Warren, Jr via dev > Sent: Thursday, October 13, 2022 14:43 > To: dev@cassandra.apache.org > Subject: Re: [Discuss] CEP-24 Password validation and generation > > NetApp Security WARNING: This is a

[DISCUSS] Remove Dead Pull Requests

At the moment we have 222 open pull requests. Some dating back 4 years. For some the repository from which they were pulled from has been deleted. For many there are branch conflicts. Now, I am new here so please excuse any misstatements and attribute to ignorance not malice any offence. I

Re: Cassandra project status update 2022-08-03

Perhaps flaky tests need to be handled differently. Is there a way to build a statistical model of the current flakiness of the test that we can then use during testing to accept the failures? So if an acceptable level of flakiness is developed then if the test fails, it needs to be run again or

Re: [DISCUSS] Remove Dead Pull Requests

t the project > has either not been able to act on at the time; or which the original > contributor started but was unable to complete. We’ve picked up many of > these after a couple years and carried them to completion. Byte-comparable > types come to mind. There are many,

Re: [DISCUSS] Remove Dead Pull Requests

écrit : > >> Those all seem like good suggestions to me >> >> On 11 Aug 2022, at 08:44, Claude Warren, Jr via dev < >> dev@cassandra.apache.org> wrote: >> >>  >> My original goal was to reduce the number of pull requests in the backlog >&g

[Proposal] add pull request template

Github provides the ability to add a pull request template [1]. I think that such a template could assist in making the pull requests better. Something like the text below, along with verifying that CASSANDRA-### will link to Jira [2], should provide the information needed and remind submitters

Re: [Proposal] add pull request template

erge it will take extra > time and care when it comes to these formalities anyway. The reason > why a PR should be merged should be the priority. > > On Mon, 15 Aug 2022 at 10:41, Claude Warren, Jr via dev > wrote: > > > > Github provides the ability to add a pull

Re: [Proposal] add pull request template

I am all for simplification. How about - start of text Issue resolved: CASSANDRA- - [ ] Jira ticket contains a description of: what is fixed, why it is needed, and what branches to apply it to. - [ ] Commits have been squashed to remove intermediate development commit

CASSANDRA-14940 and flaky tests

I started looking at the backlog of critical errors in Jira. It contains a fully working example of the issue. While it was reported under version 3.11.3 it appears to be present under 4.0.5. I don't know the "go" language but my reading of the script is that, in a single cassandra

Re: key apt by apache cassandra seems deprecated and cqlsh is broken

Could this be related to the deprecation of apt-key on your system? You don't specify what version of which distribution you are using. However, there is a good example of how to solve the issue at https://www.linuxuprising.com/2021/01/apt-key-is-deprecated-how-to-add.html On Tue, Aug 9, 2022

Re: upgrade sstable selection

on > > On Tue, Jan 10, 2023 at 4:44 AM Claude Warren, Jr via dev > wrote: > > > > Greetings, > > > > I am working on the downgradesstables code and seem to have a problem > with ordering of the downgrade or perhaps the Directories.SSTableLister > > > >

upgrade sstable selection

Greetings, I am working on the downgradesstables code and seem to have a problem with ordering of the downgrade or perhaps the Directories.SSTableLister I lifted the code from upgradesstables to select the files to downgrade. The only difference in the code that selects the files to downgrade is

Re: Aggregate functions on collections, collection functions and MAXWRITETIME

I think the semantics of the situation is important here. Let’s take MAX as our example aggregate function.. We all expect that in a DB context MAX(column) will return the value of the column with the maximum value. That is the expected semantics of MAX. The question here is that there are

Review requested: Add downgradesstables

https://github.com/apache/cassandra/pull/2045 https://issues.apache.org/jira/browse/CASSANDRA-8928 This is a work in progress and I am looking for some feedback. This fix appears to work correctly. But I think the placement of the v3 directory is probably not the best and perhaps should be

Re: [DISCUSSION] Cassandra's code style and source code analysis

rule on the documentation page [1]. > > > > [1] https://cassandra.apache.org/_/development/code_style.html > [2] https://issues.apache.org/jira/browse/CASSANDRA-17925 > [3] https://issues.apache.org/jira/browse/CASSANDRA-18089 > [4] https://github.com/apache/cassandra/pull/

Re: Aggregate functions on collections, collection functions and MAXWRITETIME

tion functions working >>> only on collections, as originally designed, and as they currently are on >>> trunk. The question is what we do with MAXWRITETIME. That function is also >>> only on trunk, and it might be repetitive given the more generic collection >&g

Weird results

I am working on a StandaloneDowngrader.java based on StandaloneUpgrader.java While working on the tests I had a problem with 2 test (testFlagArgs and testDefaultCall) that failed with: ERROR [main] 2022-12-14 10:35:20,051 SSTableReader.java:496 - Cannot open

Re: [DISCUSSION] Cassandra's code style and source code analysis

+1 for the concept as a whole. I am certain I could find nits to pick if I looked deeply. @mck -- I did have a problem with Cassandra + Eclipse + Java11 (Classpath). I gave up and am spending time trying to learn IntelliJ. I also mentioned it in one of the discussion areas. Claude On Thu,

Re: [DISCUSSION] Cassandra's code style and source code analysis

ntioned and >>> it did not work out of the box but it is definitely possible to set up >>> successfully. I do not remember the details. >>> >> >>> >> To replay to Maxim, it all seems good to me, roughly, but I humbly >>> think it all boils down to Maven/G

Re: [DISCUSS] Clear rules about sstable versioning and downgrade support

What does this mean for the Trie sstable format? Would it perhaps make sense to version the sstable upgrader (and future downgrader) based on the highest version they understand? for example sstableupgrader version N will handle the n? versions so it can upgrade from m? while sstabledowngrader

Upgrading sstables and default partitioner.

Greetings, I am working on porting a fix for table upgrade order into V3.0 and have come across the following issue: ERROR 10:23:31 Cannot open /home/claude/apache/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/me-89-big; partitioner

Re: [DISCUSSION] Cassandra's code style and source code analysis

Turn it on at warning (or lower) level now, so people have some idea of the size of change to their current code. On Wed, Jan 25, 2023 at 12:05 PM Miklosovic, Stefan < stefan.mikloso...@netapp.com> wrote: > Thank you Maxim for doing this. > > It is nice to see this effort materialized in a PR. >

Re: [DISCUSSION] Framework for Internal Collection Exposure and Monitoring API Alignment

Actually, Maxim's proposal does not depend on JMX being present or not. What the proposal does is make it easier to create/sync multiple presentations of the same internal data: Virtual Tables, JMX, Metrics, next year's greatest data presentation strategy. Removing JMX from the mix just reduces

Re: A proposal for refactoring the CircleCI config

I have been working on https://issues.apache.org/jira/projects/CASSANDRA/issues/CASSANDRA-18012 which modifies the generate.sh script for the circleci configurations. Perhaps all of this should be rolled into one change? On Fri, Nov 11, 2022 at 3:47 AM Ekaterina Dimitrova wrote: > Hey Derek, >

Re: [DISSCUSS] Access to JDK internals only after dev mailing list consensus?

This change looks good to me. It is clear and concise. On Fri, Nov 4, 2022 at 9:50 PM Ekaterina Dimitrova wrote: >  > > I finally got the chance to put down a proposal for a section at the end > of the Cassandra Code Style document. > Please help a fellow non-native speaker and definitely not

[DISCUSS] Moving standard boiler plate script blocks.

I would like to get some more eyes on https://github.com/apache/cassandra/pull/1950/files wich arises from CASSANDRA-17773 The basic idea is to: - Move the boiler plate script code to a single sourced file. - Add code to make debugging scripts easier, this in response to CASSANDRA-17773

Removing columns from sstables

Greetings, I have been looking through the code and I can't find any place where columns are removed from an sstable. I have found that rows can be deleted. Columns can be marked as deleted. But I have found no place where the deleted cell is removed from the row. Is there the concept of

Re: Removing columns from sstables

Close. It is still in the table so the v3.x code that reads system.local will detect it and fail on an unknown column as that code appears to be looking at the actual on-disk format. It sounds like the short answer is that there is no way to physically remove the column from the on-disk format

downgrade sstables

I have been working on downgrading sstables for awhile now. I have the downgrader mostly working. The only issue is when downgrading system tables. Specifically during the 3.1 -> 4.0 changes a column broadcast_port was added to system/local. This means that 3.1 system can not read the table as

[DISCUSS] Single boilerplate script

Pull request https://github.com/apache/cassandra/pull/1950/files is an attempt to move the boilerplate coding from the script files into a single maintainable file. This change does 4 things: 1. Moves the standard boiler plate from the standard scripts into a single maintainable script to

Re: Downgradability

Broken downgrading can be fixed (I think) by modifying the SearializationHeader.toHeader() method where it currently throws an UnknownColumnException. If we can, instead of throwing the exception, create a dropped column for the unexpected column then I think the code will work. I realise that

Re: Downgradability

e for it. >> I simply prefer that we take the time to do things right. >> >> Thanks to Scott and you, downgradability got a much better visibility so >> no matter what approach we pick, I am convinced that we will get there. >> >> Le jeu. 23 févr. 2023

Re: Downgradability

My goal in implementing CASSANDRA-8928 was to be able to take the current version 4.x and write it as the earliest 3.x version possible. The reasoning being that if that was possible then whatever 3.x version was

[DISCUSS] Initial implementation of cassandra-conf with nodetool example

The pull request [1] is a proposed fix for CASSANDRA-17773. I am looking for comments and a decision as to whether to move forward or not with this change. The goal is to remove much of the boiler-plate code from scripts without changing their functionality or arguments and to add the ability to

[COMPRESSION PARAMETERS] Question

Currently the compression parameters has an option called enable. When enable=false all the other options have to be removed. But it seems to me that we should support enabled=false without removing all the other parameters so that users can disable the compression for testing or problem

Re: Cassandra CI Status 2023-01-07

New Failures from Build Lead Week 5 *** CASSANDRA-18198 - "AttributeError: module 'py' has no attribute 'io'" reported in multiple tests - reported in 4.1, 3.11, and 3.0 - identified as a possible class loader issue associated with CASSANDRA-18150 *** CASSANDRA-18191 - Native Transport SSL tests

Bloom filter calculation

Can someone explain to me how the Bloom filter table in BloomFilterCalculations was derived and how it is supposed to work? As I read the table it seems to indicate that with 14 hashes and 20 bits you get a fp of 6.71e-05. But if you plug those numbers into the Bloom filter calculator [1], that

Re: Bloom filter calculation

positive rate of a bloom > filter of 20 bits with 10 entries, which means only 2 bits per entry? > > On 11 Jul 2023, at 07:14, Claude Warren, Jr via dev < > dev@cassandra.apache.org> wrote: > >  > Can someone explain to me how the Bloom filter table in > BloomFilter

Re: [DISCUSS] Bring cassandra-harry in tree as a submodule

Since the talk was not accepted for Cassandra Summit, would it be possible to record it as a simple youtube video and publish it so that the detailed information about how to use Harry is not lost? On Thu, May 25, 2023 at 7:36 AM Alex Petrov wrote: > While we are at it, we may also want to pull

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

I think that we can get more developers interested if there are available javadocs. While many of the core classes are not going to be touched by someone just starting, being able to understand what the external touch points are and how they interact with other bits of the system can be

[DISCUSS] Tiered Storage

I have been thinking about tiered storage wherein infrequently used data can be moved off to slow (cold) storage (like S3). I think that CEP-17 in conjunction with CEP-21 provides an opportunity for an interesting approach. As I understand it CEP-17 clarified the SSTables interface(s) so that

[DISCUSS] Standalone downgrader

I have an open pull request [1] to merge in a standalone downgrader. The problem has been that between v3 and v4 there was a breaking change in the system local table where the columns "broadcast_port", "listen_port", and "rpc_port" were added. The code (in the current pull request) provides

Re: [DISCUSS] Replace Sigar with OSHI (CASSANDRA-16565)

Can I get an another review/approval for the pull request? https://github.com/apache/cassandra/pull/2842/files On Fri, Dec 15, 2023 at 4:04 AM guo Maxwell wrote: > +1 too > > Mick Semb Wever 于2023年12月15日周五 10:01写道： > >> >> >> >>> >>> Are there objections to making this switch and adding a new

Re: [DISCUSS] Replace Sigar with OSHI (CASSANDRA-16565)

The pull request is : https://github.com/apache/cassandra/pull/2842 On Mon, Dec 18, 2023 at 10:26 AM Mick Semb Wever wrote: > > > Can I get an another review/approval for the pull request? >> https://github.com/apache/cassandra/pull/2842/files >> > > > It is not clear on the ticket what is

[DISCUSS] Replace Sigar with OSHI (CASSANDRA-16565)

Greetings, I have submitted a pull request[1] that replaces the unsupported Sigar library with the maintained OSHI library. OSHI is an MIT licensed library that provides information about the underlying OS much like Sigar did. The change adds a dependency on oshi-core at the following

Re: Custom FSError and CommitLog Error Handling

I can see this as a strong improvement in Cassandra management and support it. +1 non binding On Mon, Dec 11, 2023 at 8:28 PM Raymond Huffman wrote: > Hello All, > > On our fork of Cassandra, we've implemented some custom behavior for > handling CommitLog and SSTable Corruption errors.

Re: Call for Presentations closing soon: Community over Code EU 2024

Additionally, if you have a talk about some underlying technology that could be applicable across multiple projects submit it or a poster based on it. We are looking for good cross-project presentations. Claude Chair, Community over Code, EU 2024. On Mon, Jan 8, 2024 at 8:24 PM Paulo Motta

Re: [DISCUSS] CASSANDRA-19104: Standardize tablestats formatting and data units

Why not change the option so that -H will operate as it does now while -Hn (where n is a digit) will limit the number of decimal places to n. On Mon, Dec 4, 2023 at 5:11 PM Brad wrote: > Thanks, Jacek. Using three significant digits for disk space is a good > suggestion. > > On Mon, Dec 4,

[DISCUSS] Update cassandra-stress to use Apache Commons CLI (CASSANDRA-18661)

I have been working on CASSANDRA-18661 to see if it is possible to migrate to the Apache commons-cli as noted in the ticket. It is possible to do so, and after several pull requests to commons-cli, I have managed to migrate the settings of the stress tool. We will have to wait for commons-cli

Patently invalid Compression parameters in CompressedSequentialWriterTest

I have been working at cleaning up the Yaml configuration for default table compression settings and found that the CompressedSequentialWriterTest uses some parameters that are outside the acceptable limits (like bufferLength not a power of 2, or maxCompressedLength > bufferLength). I can

Default table compression defined in yaml.

After much work by several people, I have pulled together the changes to define the default compression in the cassandra.yaml file and have created a pull request [1]. If you are interested this in topic, please take a look at the changes and give at least a cursory review. [1]

Re: Default table compression defined in yaml.

precated format only to be > removed at a later version? > > > On 18/03/2024 14:39, Claude Warren, Jr via dev wrote: > > After much work by several people, I have pulled together the changes to > define the default compression in the cassandra.yaml file and have created > a pull

Re: Default table compression defined in yaml.

t;> deprecated, and the new format is `foobar: 123KiB`. Is there a need to >> introduce new settings entries with the deprecated format only to be >> removed at a later version? >> >> >> On 18/03/2024 14:39, Claude Warren, Jr via dev wrote: >> >> Aft

Re: Default table compression defined in yaml.

in_kb: 123` format in the cassandra.yaml file is >>> deprecated, and the new format is `foobar: 123KiB`. Is there a need to >>> introduce new settings entries with the deprecated format only to be >>> removed at a later version? >>> >>> >>> On 18/03

Re: Default table compression defined in yaml.

table" key sounds good to me. > > - - -- --- ----- - > Jacek Lewandowski > > > czw., 21 mar 2024 o 08:32 Claude Warren, Jr via dev < > dev@cassandra.apache.org> napisał(a): > >> Jacek, >> >> I am a bit confused here. I find a k

Re: [DISCUSS] CEP-40: Data Transfer Using Cassandra Sidecar for Live Migrating Instances

I think this solution would solve one of the problems that Aiven has with node replacement currently. Though TCM will probably help as well. On Mon, Apr 15, 2024 at 11:47 PM German Eichberger via dev < dev@cassandra.apache.org> wrote: > Thanks for the proposal. I second Jordan that we need more

Re: discuss: add to_human_size function

I like the idea. Is the intention to have the of the function be parsable by the config parsers like DataRateSpec, DataStorageSpec, or DurationSpec? Claude On Thu, Apr 18, 2024 at 9:47 PM Ariel Weisberg wrote: > Hi, > > I think it’s a good quality of life improvement, but I am someone who >

Re: discuss: add to_human_size function

ture, we might also add to_human_duration which would be > implemented against DurationSpec so similar conversions are possible. > > On Fri, Apr 19, 2024 at 10:53 AM Claude Warren, Jr via dev < > dev@cassandra.apache.org> wrote: > >> I like the idea. Is the intention to ha

  1   2   >