Re: CCM and CASSANDRA_USE_JDK11

BTW. I've created a simple workflow for GitHub Actions - https://github.com/riptano/ccm/pull/771 - feel free to review - - -- --- - - Jacek Lewandowski sob., 25 maj 2024 o 06:09 Jacek Lewandowski napisał(a): > Thank you for all the opinions. That is useful for fut

Re: CCM and CASSANDRA_USE_JDK11

h we do when testing upgrades. Such simplification would also remove some clutter from the logs. Can you remember the whole environment logged frequently and twice when running a node? Can we make this discussion conclusive? Thanks! - - -- --- - ---- ----- Jacek Lewandowski pt., 24 m

CCM and CASSANDRA_USE_JDK11

configured for Java 11, we have to have CASSANDRA_USE_JDK11 and if not, we cannot have it. Therefore, CCM can be based solely on the current Java version and not include the existence of CASSANDRA_USE_JDK11 in the Java version selection process. WDYT? - - -- --- - - Jacek

Re: [DISCUSS] ccm as a subproject

+1 (my personal opinion) How to deal with the DSE-supporting code is a separate discussion IMO - - -- --- - - Jacek Lewandowski czw., 16 maj 2024 o 10:21 Berenguer Blasi napisał(a): > +1 ccm is super useful > On 16/5/24 10:09, Mick Semb Wever wrote: > >

Re: Schema Disagreement Issue for Cassandra 4.1

- - -- --- - - Jacek Lewandowski wt., 2 kwi 2024 o 20:26 Cheng Wang via dev napisał(a): > And it seems that the main fix for the > https://issues.apache.org/jira/browse/CASSANDRA-18291 is to change the > order of updating the schema version in the system.lo

Re: Schema Disagreement Issue for Cassandra 4.1

Please cc me when you create a ticket pon., 1 kwi 2024, 14:13 użytkownik Bowen Song via dev < dev@cassandra.apache.org> napisał: > It sounds worthy of a Jira ticket. > > On 01/04/2024 06:23, Cheng Wang via dev wrote: > > Hello, > > > > I have recently encountered a problem concerning schema

Re: Default table compression defined in yaml.

nt is that we should not add to that mess and try to group the new stuff. "default_compression" under ""sstable" key sounds good to me. - - -- --- - - Jacek Lewandowski czw., 21 mar 2024 o 08:32 Claude Warren, Jr via dev < dev@cassandra.apache.or

Re: Default table compression defined in yaml.

Compression params for sstables should be under the "sstable" key. - - -- --- - ----- Jacek Lewandowski wt., 19 mar 2024 o 13:10 Ekaterina Dimitrova napisał(a): > Any new settings are expected to be added in the new format > > On Tue, 19 Mar 2024 at 5

[DISCUSS] Types compatibility

Hey, I was going through the different kinds of types compatibility and found that I need help in understanding them. Therefore, I tried to figure out what is used where, in particular, what means that two types are "compatible", "valueCompatible" or "serializationCompatible". I found

Re: Welcome Brad Schoening as Cassandra Committer

Congrats Brad! - - -- --- - - Jacek Lewandowski czw., 22 lut 2024 o 01:29 Štefan Miklošovič napisał(a): > Congrats Brad, great work in the Python department :) > > On Wed, Feb 21, 2024 at 9:46 PM Josh McKenzie > wrote: > >> The Apache Cas

Re: [Discuss] Improving CI workflows

Let's not start another thread and discuss that directly on the ticket. - - -- --- - - Jacek Lewandowski wt., 20 lut 2024 o 11:31 Berenguer Blasi napisał(a): > Hi All, > > after the recent discussion that came up in CASSANDRA-18753's discuss > thre

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

We should conclude this discussion by answering Branimir's original question.* I vote for merging that and exposing issues to the CI.* For pre-commit optimization I've opened https://issues.apache.org/jira/browse/CASSANDRA-19406 epic and we should add exact tasks there to make this valuable

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

Brandon, that should be doable with the current filters I think - that is, select only those tests which do not support vnodes. Do you know about such in-jvm dtests as well? - - -- --- - - Jacek Lewandowski czw., 15 lut 2024 o 18:21 Brandon Williams napisał

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

Great summary Josh, > >- JDK-based test suites on highest supported jdk using other config > > Do you mean a smoke test suite by that ^ ? - - -- --- - ----- Jacek Lewandowski czw., 15 lut 2024 o 18:12 Josh McKenzie napisał(a): > Would it make sens

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

I fully understand you. Although I have that luxury to use more containers, I simply feel that rerunning the same code with different configurations which do not impact that code is just a waste of resources and money. - - -- --- - - Jacek Lewandowski czw., 15 lut 2024

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

h and minimally require precommit tests for that configuration. >> Assignees and reviewers can determine if additional test variants are >> required based on the patch scope. >> >> Nightly and prerelease tests can be run to catch any issues outside the >> standard

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

śr., 14 lut 2024 o 17:30 Josh McKenzie napisał(a): > When we have failing tests people do not spend the time to figure out if > their logic caused a regression and merge, making things more unstable… so > when we merge failing tests that leads to people merging even more failing > tests... > >

Re: [Discuss] Introducing Flexible Authentication in Cassandra via Feature Flag

to let the administrators enable/disable and reconfigure authentication without a restart so we could discuss whether such transitional mode would be needed at all in that case. Thanks, - - -- --- - - Jacek Lewandowski wt., 13 lut 2024 o 07:04 Jeff Jirsa napisał

Re: [Discuss] "Latest" configuration for testing and evaluation (CASSANDRA-18753)

We should not block merging configuration changes given it is a valid configuration - which I understand as it is correct, passes all config validations, it matches documented rules, etc. And this provided latest config matches those requirements I assume. The failures should block release or we

Re: Welcome Maxim Muzafarov as Cassandra Committer

Congratulations Maxim, well deserved, it's a pleasure to work with you! - - -- --- - - Jacek Lewandowski pon., 8 sty 2024 o 19:35 Lorina Poland napisał(a): > Congratulations Maxim! > > On 2024/01/08 18:19:04 Josh McKenzie wrote: > > The Apache Cassandra

Re: Harry in-tree (Forked from "Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?")

Obviously +1 Thank you Alex pt., 22 gru 2023, 16:45 użytkownik Sumanth Pasupuleti < sumanth.pasupuleti...@gmail.com> napisał: > +1, thank you for your efforts in bringing Harry in-tree. Anything that > improves the testing ecosystem for Cassandra, particularly around complex > scenarios / edge

Re: [ATTENTION] Forced push on cassandra-5.0 branch !!!

no such merge (I pushed this branch also to my personal fork: https://github.com/jacek-lewandowski/cassandra/commits/cassandra-5.0) I am really curious about what went wrong as I want to avoid that in the future - - -- --- - - Jacek Lewandowski niedz., 17 gru 2023 o 05:00

Moving Semver4j from test to main dependencies

for it. Maybe at some point we can replace our custom implementation of CassandraVersion as well. Thanks, - - -- --- - - Jacek Lewandowski

Re: Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?

les of how this would actually > benefit our test suites? > > On 12 Dec 2023, at 10:51, Jacek Lewandowski > wrote: > >  > I have two major pros for JUnit 5: > - much better support for parameterized tests > - global test hooks (automatically detectable extensions) + > mul

Re: Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?

less well justified, which it may be - > just not immediately obvious to me. > > On 11 Dec 2023, at 08:33, Jacek Lewandowski > wrote: > >  > Nobody referred so far to the idea of moving to JUnit 5, what are the > opinions? > > > > niedz., 10 gru 2023 o 11:03

Re: Ext4 data corruption in stable kernels

, just that some stable kernels are affected. Adding to the > problem is that it might be vendor specific as well. For example, RH might > backport an upstream patch in the kernel they ship that's non-standard. > > Hopefully someone compiles a list. > > Jon > > On Mon, Dec 11, 2023

Re: Ext4 data corruption in stable kernels

Aren't only specific kernels affected? If we can detect the kernel version, the feature can be force disabled with the problematic kernels pon., 11 gru 2023, 20:45 użytkownik Jon Haddad napisał: > Hey folks, > > Just wanted to raise awareness about a I/O issue that seems to be > affecting some

Re: Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?

Nobody referred so far to the idea of moving to JUnit 5, what are the opinions? niedz., 10 gru 2023 o 11:03 Benedict napisał(a): > Alex’s suggestion was that we meta randomise, ie we randomise the config > parameters to gain better rather than lesser coverage overall. This means > we cover

Re: Welcome Mike Adamson as Cassandra committer

Awesome, congratulations Mike !!! - - -- --- - - Jacek Lewandowski pt., 8 gru 2023 o 16:10 Miklosovic, Stefan via dev napisał(a): > Wow, great news! Congratulations on your committership, Mike. > > > From: Be

Re: Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?

> > It would be great to setup a JUnitRunner using the simulator and find out > though. > I like this idea - this is what I meant when asking about the current unit tests - to me, a test is either simulation or a fuzz. Due to pretty random execution order of unit tests, all of them can be

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

This looks great, I'd consider limiting the number of significant digits to 3 in the human readable format. In the above example it would translate to: Space used (live): 1.46 TiB Space used (total): 1.46 TiB Bytes repaired: 0.00 KiB Bytes unrepaired: 4.31 TiB Bytes pending repair: 0.000 KiB I

Re: Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?

Thanks for the exhaustive response, Alex :) Let me bring my point of view: 1. Since long tests are just unit tests that take a long time to run, it makes sense to separate them for efficient parallelization in CI. Since we are adding new tests, modifying the existing ones, etc., that should be

Re: Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?

he/cassandra/pull/2554/files#diff-a4c4d1d91048841f76d124386858bda9944644cfef8ccb4ab84319cedaf5b3feR237-R267> > would make things a lot easier to wrap our heads around and maintain I > think. > > As for what qualifies as burn vs. long... /shrug couldn't tell you. Would > have to go do

Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?

Hi, I'm getting a bit lost - what are the exact differences between those test scenarios? What are the criteria for qualifying a test to be part of a certain scenario? I'm working a little bit with tests and build scripts and the number of different configurations for which we have a separate

Re: [VOTE] Release Apache Cassandra 5.0-beta1

> > If we end up not releasing a final 5.0 artifact by a Cassandra Summit it > will signal to the community that we’re prioritizing stability and it could > be a good opportunity to get people to test the beta or RC before we stamp > it as production ready. > I agree with Paulo's comment czw.,

Re: Welcome Francisco Guerrero Hernandez as Cassandra Committer

Congrats!!! wt., 28 lis 2023, 23:08 użytkownik Abe Ratnofsky napisał: > Congrats Francisco! > > > On Nov 28, 2023, at 1:56 PM, C. Scott Andreas > wrote: > > > > Congratulations, Francisco! > > > > - Scott > > > >> On Nov 28, 2023, at 10:53 AM, Dinesh Joshi wrote: > >> > >> The PMC members

Re: Include CASSANDRA-18464 in 5.0-beta1 (direct I/O support for commitlog write)

Should I assume it's an agreement? - - -- --- - - Jacek Lewandowski wt., 28 lis 2023 o 12:05 Mick Semb Wever napisał(a): > > > So, assuming beta2, can it be merged to cassandra-5.0 now? >> > > > Yes from me. > And I would interpret Brand

Re: Include CASSANDRA-18464 in 5.0-beta1 (direct I/O support for commitlog write)

So, assuming beta2, can it be merged to cassandra-5.0 now? - - -- --- - - Jacek Lewandowski pon., 27 lis 2023 o 16:02 Mick Semb Wever napisał(a): > > I don't want to veto the 5.0-beta1 release for this. > > I would rather cut and include it in the nex

Re: [DISCUSS] Harry in-tree

+1 - - -- --- - - Jacek Lewandowski pon., 27 lis 2023 o 22:11 Ekaterina Dimitrova napisał(a): > +1, also, Alex, just an idea - maybe you want to make a virtual talk, as > part of the contributors meetings? > > > На понеделник, 27 ноември 2023 г. Yi

Re: [VOTE] Release Apache Cassandra 5.0-beta1

I propose to consider including https://issues.apache.org/jira/browse/CASSANDRA-18464 (started a separate thread) pon., 27 lis 2023 o 13:06 Benjamin Lerer napisał(a): > Looking at the board it is unclear to me why CASSANDRA-19011 > ,

Include CASSANDRA-18464 in 5.0-beta1 (direct I/O support for commitlog write)

Hey, I'd like to ask if we can include https://issues.apache.org/jira/browse/CASSANDRA-18464 in the 5.0-beta1 release. This introduces the ability to write to the commitlog using direct I/O and bringing some noticeable performance improvements when enabled (disabled by default). Since it

Re: CEP-21 - Transactional cluster metadata merged to trunk

Hi, I'm happy to hear that the feature got merged. Though, I share Benjamin's worries about that being a bad precedent. I don't think it makes sense to do repeated runs in this particular case. Detecting flaky tests would not prove anything; they can be caused by this patch, but we would not

Re: Push TCM (CEP-21) and Accord (CEP-15) to 5.1 (and cut an immediate 5.1-alpha1)

accordingly to participate in the remaining work. Thanks, - - -- --- - - Jacek Lewandowski pt., 27 paź 2023 o 10:26 Benjamin Lerer napisał(a): > I would be interested in testing Maxim's approach. We need more visibility > on big features and their progress to impro

Re: [VOTE] Release Apache Cassandra 5.0-alpha1 (take3)

Ok, +1 czw., 7 wrz 2023, 21:33 użytkownik Mick Semb Wever napisał: > > > On Thu, 7 Sept 2023 at 13:53, Jacek Lewandowski < > lewandowski.ja...@gmail.com> wrote: > >> Mick, is the documentation / website ok? >> > > > Can you elaborate on what is ok

Re: [VOTE] Release Apache Cassandra 5.0-alpha1 (take3)

Mick, is the documentation / website ok? If so, +1 Best Regards, - - -- --- - - Jacek Lewandowski czw., 7 wrz 2023 o 12:58 Brandon Williams napisał(a): > +1 > > Kind Regards, > Brandon > > On Mon, Sep 4, 2023 at 3:26 PM Mick Semb Wever wrote: >

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

With or without outputting JavaDoc to HTML, there are some errors which we should maybe fix. We want to keep the documentation, but there can be syntax errors which may prevent IDE generating a proper preview. So, the question is - should we validate the JavaDoc comments as a precommit task? Can

Re: Fwd: [DISCUSS] Formalizing requirements for pre-commit patches on new CI

., 12 lip 2023 o 14:52 Jacek Lewandowski napisał(a): > Would it be re-opening the ticket or creating a new ticket with "revert of > fix" ? > > > > śr., 12 lip 2023 o 14:51 Ekaterina Dimitrova > napisał(a): > >> jenkins_jira_integration >> <http

Re: Fwd: [DISCUSS] Formalizing requirements for pre-commit patches on new CI

y 2 effort and define packages in >> the primary codebase where changes take place and multiplex (on a smaller >> scale) their respective packages of unit tests in the future if we see >> problems in this area. >> >> Flakey tests are a giant pain in the ass and a huge d

Re: Fwd: [DISCUSS] Formalizing requirements for pre-commit patches on new CI

Isn't novnodes a special case of vnodes with n=1 ? We should rather select a subset of tests for which it makes sense to run with different configurations. The set of configurations against which we run the tests currently is still only the subset of all possible cases. I could ask - why don't

Re: [DISCUSS] When to run CheckStyle and other verificiations

; just gotten sidetracked by things and also realized how little I've >> actually modified locally since I just run most of the linting against >> delta'ed files only to keep my changed work in compliance. Still a very >> noisy mess when SpotBugs is run against the entire codebase

Re: [DISCUSS] When to run CheckStyle and other verificiations

>>> I'm not saying what you've proposed is bad, in fact, we're not >>> currently doing the pipeline I'm talking about, but adding an >>> additional endpoint is something we should consider very carefully as >>> it may create some difficulties for Maven/G

Re: [DISCUSS] Limiting query results by size (CASSANDRA-11745)

eturned to the user when the full row > is queried without transformation. For all the other case the difference > can be really significant. For a group by queries doing a count(*), the > approach suggested will return a page size that is totally off with what > was requested. > > Le

Re: [DISCUSS] When to run CheckStyle and other verificiations

rina >>> >>> On Thu, 29 Jun 2023 at 10:52, Josh McKenzie >>> wrote: >>> >>> >>> I really prefer separate tasks than flags. Flags are not listed in the >>> help message like "ant -p" and are not auto-completed in t

Re: [DISCUSS] Formalizing requirements for pre-commit patches on new CI

Perhaps pre-commit checks should include mostly the typical configuration of Cassandra rather than some subset of possible combinations. Like it was said somewhere above - test with the default number of vnodes, test with the default compression settings, and test with the default heap/off-heap

Re: [DISCUSS] When to run CheckStyle and other verificiations

> > On Thu, Jun 29, 2023 at 3:22 AM Jacek Lewandowski > wrote: > > > > So given all the feedback, I'm going to do the following: > > > > "jar" will depend on "check" target > > "build-project", "build-test" and "te

Re: [DISCUSS] When to run CheckStyle and other verificiations

nd eclipse-warnings There is an additional flag "no-check" to disable checks in the "jar" target. Will not introduce any Git hook. wt., 27 cze 2023 o 18:35 Jacek Lewandowski napisał(a): > With git you can always opt-out by adding --no-verify flag to either push > or commi

Re: [DISCUSS] When to run CheckStyle and other verificiations

With git you can always opt-out by adding --no-verify flag to either push or commit I really prefer separate tasks than flags. Flags are not listed in the help message like "ant -p" and are not auto-completed in the terminal. That makes them almost undiscoverable for newcomers. Want to have jar

Re: [DISCUSS] When to run CheckStyle and other verificiations

not be the best one is valid, and we should rather think about pre-commit - - -- --- - - Jacek Lewandowski wt., 27 cze 2023 o 09:25 Miklosovic, Stefan napisał(a): > I am doing all git-related operations in the console / bash (IDEA > terminal, alt+f12 in IDEA). I know ID

Re: [DISCUSS] When to run CheckStyle and other verificiations

recognize the sender and know the content is >> safe. >> >> >> >> not running it automatically with the targets which devs usually run >> locally. >> >> The checks tend to have an opt-out, such as -Dno-checkstyle=true… so its >> really

Re: [DISCUSS] When to run CheckStyle and other verificiations

That would work as well Brandon, basically what is proposed in CASSANDRA-18618, that is "check" target, actually needs to build the project to perform some verifications - I suppose running "ant check" should be sufficient. - - -- --- - ---- ----- Jacek Lewand

Re: [DISCUSS] When to run CheckStyle and other verificiations

consistently by adding a Git hook. Do you think we can encounter some particular problems with this approach? Maxim, this is a great idea, and I fully support it - but this does not address the issues I've raised there. - - -- --- - - Jacek Lewandowski pon., 26 cze 2023 o 14:05

Re: [DISCUSS] When to run CheckStyle and other verificiations

Yes, I've mentioned that there is a property we can set to skip checkstyle. Currently such a goal is "artifacts" which basically validates everything. - - -- --- - ----- Jacek Lewandowski pon., 26 cze 2023 o 13:09 Mike Adamson napisał(a): > While I

[DISCUSS] When to run CheckStyle and other verificiations

and do not even touch Ant commands directly Checks can take time; to optimize that, they could be enforced locally to verify only the modified files in the same way as we currently determine the tests to be repeated for CircleCI. Thanks - - -- --- - - Jacek Lewandowski

Re: [DISCUSSIONS] Replace ant eclipse-warnings with CheckerFramework

Later, we may enable more checks than just leaked resources to improve the code gradually. - - -- --- - - Jacek Lewandowski pt., 16 cze 2023 o 13:48 Ekaterina Dimitrova napisał(a): > Got so excited that I forgot to say which of the two options exactly I >

Re: [DISCUSSIONS] Replace ant eclipse-warnings with CheckerFramework

Additional question is whether we want to run the checks against the whole project or just against the file changes between the feature branch and the target release branch? - - -- --- - - Jacek Lewandowski pt., 16 cze 2023 o 13:09 Aleksey Yeshchenko napisał

Re: [DISCUSS] Limiting query results by size (CASSANDRA-11745)

Josh, that answers my question exactly; thank you. I will not implement limiting the result set in CQL (that is, by LIMIT clause) and stay with just paging. Whether the page size is defined in bytes or rows can be determined by a flag - there are many unused bits for that. So my other question -

Re: [DISCUSS] Limiting query results by size (CASSANDRA-11745)

then is > is really confusing and can be a problem for some usecases. We have users > keeping their session open and the page information to display page of data. > > Le lun. 12 juin 2023 à 09:08, Jacek Lewandowski < > lewandowski.ja...@gmail.com> a écrit : > >> Hi, &g

Re: [DISCUSS] Limiting query results by size (CASSANDRA-11745)

the resultset, or we instead want to use this >> mechanism to limit the amount of memory used internally for the data and >> prevent problems (assuming restricting size and rows number can be used >> simultaneously in a way that we stop when we reach any of the specified >> limits). >> >> https://issues.apache.org/jira/browse/CASSANDRA-11745 >> >> thanks, >> - - -- --- - - >> Jacek Lewandowski >> >

[DISCUSS] Limiting query results by size (CASSANDRA-11745)

SANDRA-11745 thanks, - - -- --- - ---- ----- Jacek Lewandowski

[DISCUSS] CEP-31 negotiated authentication

+and+authorization thanks, - - -- --- - - Jacek Lewandowski

Re: [CASSANDRA-11471] Authentication mechanism negotiation (OPTIONS/SUPPORTED)

a separate thread on that topic soon. thanks - - -- --- - - Jacek Lewandowski pt., 26 maj 2023 o 04:08 Dinesh Joshi napisał(a): > Leaving the naming aside (the hardest part of any software), I am > generally positive about your idea. A protocol version bu

Re: [EXTERNAL] Re: (CVE only) support for 3,11 beyond published EOL

of validation whether that effort is justified. btw. We have recently agreed to keep support for M sstables format (3.0 - 3.11). thanks, - - -- --- - - Jacek Lewandowski czw., 13 kwi 2023 o 21:59 Mick Semb Wever napisał(a): > Yes, this would be great. Right now us

Re: [DISCUSS] Introduce DATABASE as an alternative to KEYSPACE

config, like simple 1, so that creating a names boils down to a simply CREATE KEYSPACE|SCHEMA|DATABASE|NAMESPACE ; thanks, - - -- --- - - Jacek Lewandowski czw., 6 kwi 2023 o 04:09 guo Maxwell napisał(a): > either KEYSPACE or DATABASE or SCHEMA is better than NAMESP

Re: [DISCUSS] Introduce DATABASE as an alternative to KEYSPACE

While for someone who already knows Cassandra keyspace is something natural, for newcomers it is yet another concept to understand. If namespace is used in PostgreSQL, it sounds even better to me. Thanks, - - -- --- - - Jacek Lewandowski wt., 4 kwi 2023 o 19:07 Rahul

Re: [VOTE] CEP-26: Unified Compaction Strategy

+1 - - -- --- - - Jacek Lewandowski wt., 4 kwi 2023 o 15:01 Berenguer Blasi napisał(a): > +1 > On 4/4/23 14:36, J. D. Jordan wrote: > > +1 > > On Apr 4, 2023, at 7:29 AM, Brandon Williams > wrote: > >  > +1 > > On Tue, Apr 4,

Re: [DISCUSS] Moving system property names to the CassandraRelevantProperties

I'll do - - -- --- - - Jacek Lewandowski czw., 30 mar 2023 o 22:09 Miklosovic, Stefan napisał(a): > Hi list, > > we are looking for one more committer to take a look at this patch (1, 2). > > It looks like there is a lot to go through because of

Re: Welcome our next PMC Chair Josh McKenzie

Congrats Josh! - - -- --- - - Jacek Lewandowski czw., 23 mar 2023 o 09:32 Berenguer Blasi napisał(a): > Congrats Josh! > On 23/3/23 9:22, Mick Semb Wever wrote: > > It is time to pass the baton on, and on behalf of the Apache Cassandra > Project Manag

Re: [DISCUSS] Drop support for sstable formats m* (in trunk)

people are still on 3.11 and we should not make their life harder when they consider upgrading directly to 5.0. Though clear rules for that would help the users and us. thanks, - - -- --- - - Jacek Lewandowski wt., 14 mar 2023 o 15:36 C. Scott Andreas napisał(a): >

Re: Should we cut some new releases?

+1 pon., 13 mar 2023, 20:36 użytkownik Miklosovic, Stefan < stefan.mikloso...@netapp.com> napisał: > Yes, I was waiting for CASSANDRA-18125 to be in. > > I can release 4.1.1 to staging tomorrow morning CET if nobody objects that. > > Not sure about 4.0.9. We released 4.0.8 just few weeks ago. I

Re: Role of Hadoop code in Cassandra 5.0

I've experimentally added https://issues.apache.org/jira/browse/CASSANDRA-16984 to https://issues.apache.org/jira/browse/CASSANDRA-18306 (post 4.0 cleanup) - - -- --- - - Jacek Lewandowski pt., 10 mar 2023 o 09:56 Berenguer Blasi napisał(a): > +1 deprecate + remo

Re: Role of Hadoop code in Cassandra 5.0

Is there a ticket for that? - - -- --- - - Jacek Lewandowski czw., 9 mar 2023 o 20:27 Mick Semb Wever napisał(a): > > > On Thu, 9 Mar 2023 at 18:54, Brandon Williams wrote: > >> I think if we reach consensus here that decides it. I too vote to >

Re: Role of Hadoop code in Cassandra 5.0

Is it possible to deprecate it in the 4.1.x patch release? :) - - -- --- - - Jacek Lewandowski czw., 9 mar 2023 o 18:11 Brandon Williams napisał(a): > This is my feeling too, but I think we should accomplish this by > deprecating it first. I don't expect an

Re: Role of Hadoop code in Cassandra 5.0

Lewandowski czw., 9 mar 2023 o 18:08 Jacek Lewandowski napisał(a): > I vote for removing it entirely. > > thanks > - - -- --- - ----- > Jacek Lewandowski > > > czw., 9 mar 2023 o 18:07 Miklosovic, Stefan > napisał(a): > >> Derek, >> >&

Re: Role of Hadoop code in Cassandra 5.0

I vote for removing it entirely. thanks - - -- --- - - Jacek Lewandowski czw., 9 mar 2023 o 18:07 Miklosovic, Stefan napisał(a): > Derek, > > I have couple more points ... I do not think that extracting it to a > separate repository is "win".

Re: Downgradability

A bit of organization - I've created https://issues.apache.org/jira/browse/CASSANDRA-18300 epic to track tickets related to the downgradability. Please add the tickets you are aware of. thanks - - -- --- - - Jacek Lewandowski czw., 23 lut 2023 o 17:47 Benedict napisał

Merging CEP-17

gonna merge it this week. I'm also open for doing some follow-up work if something is missing or something more is needed. Thanks, - - -- --- - - Jacek Lewandowski

Re: Downgradability

Running upgrade tests backwards is great idea which does not require extra work. For stats metadata it already supports writing in previous serialization version We need a small fix in compression metadata and that's it. A flag with the write format version is probably LHF. Maybe let's try,

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

I suppose it can be easy for the existing feature branches if they have a single commit. Don't we need to adjust each commit for multi-commit feature branches? śr., 22 lut 2023, 19:48 użytkownik Maxim Muzafarov napisał: > Hello everyone, > > I have created an issue CASSANDRA-18277 that may help

Re: Downgradability

ranges, like one impl for ma-nz, other for oa+, etc. without having a confusing implementation with a lot of conditional blocks. Old formats in such case could be maintained separately from the main code and easily switched any time. thanks - - -- --- - - Jacek Lewandowski

Re: [VOTE] CEP-21 Transactional Cluster Metadata

+1 - - -- --- - - Jacek Lewandowski wt., 7 lut 2023 o 10:12 Benjamin Lerer napisał(a): > +1 > > Le mar. 7 févr. 2023 à 06:21, a écrit : > >> +1 nb >> >> On Feb 6, 2023, at 9:05 PM, Ariel Weisberg wrote: >> >> +1 &

Re: Welcome Patrick McFadin as Cassandra Committer

Congrats !!! - - -- --- - - Jacek Lewandowski czw., 2 lut 2023 o 19:10 Melissa Logan napisał(a): > Congrats, Patrick! > > On Thu, Feb 2, 2023 at 9:58 AM Benjamin Lerer wrote: > >> The PMC members are pleased to announce that Patrick Mc

Re: Merging CEP-15 to trunk

/index.html but for unreleased Cassandra version or a blog post, so that the syntax is known to the users and they can quickly get into speed, hopefully reporting any problems soon. - - -- --- - - Jacek Lewandowski On Mon, 16 Jan 2023 at 17:52, Benedict wrote: > That’s f

[DISCUSS] Clear rules about sstable versioning and downgrade support

with version (X-1)* and X* (which means that all the minor future versions X. Perhaps we could make some commitment to change major sstable format only with new major release? What do you think? Thanks - - -- --- - - Jacek Lewandowski

Re: Introducing mockito-inline library among test dependencies

Will it work with Java17? czw., 12 sty 2023, 12:56 użytkownik Brandon Williams napisał: > +1 > > Kind Regards, > Brandon > > On Wed, Jan 11, 2023 at 2:02 PM Miklosovic, Stefan > wrote: > > > > Hi list, > > > > the test for (1) is using mockito-inline dependency for mocking static > methods as

Re: upgrade sstable selection

like the mentioned compactor would get wrong order. I suggest creating a ticket and fix the upgrader code by explicitly ordering sstables by their id. The comparator for SSTableId is available in SSTableIdFactory.COMPARATOR. Thanks, - - -- --- - - Jacek Lewandowski On Tue

Re: [VOTE] CEP-25: Trie-indexed SSTable format

+1 - - -- --- - - Jacek Lewandowski On Mon, Dec 19, 2022 at 2:00 PM Branimir Lambov wrote: > Hi everyone, > > I'd like to propose CEP-25 for approval. > > Proposal: > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-25%3A+Trie-inde

Re: Review requested: Add downgradesstables

Hi, The feature looks useful to me Could you add the pull request address to the ticket and summarize the features it is going to provide? Thank you, - - -- --- - - Jacek Lewandowski On Fri, Dec 9, 2022 at 10:13 AM Claude Warren, Jr via dev < dev@cassandra.apache.

Re: [DISCUSS] CEP-25: Trie-indexed SSTable format

+1 for the proposal ! btw. regarding tests - perhaps we will have to let Python DTests run with either new or old format thanks - - -- --- - - Jacek Lewandowski On Mon, Nov 21, 2022 at 3:06 PM Benedict wrote: > Yes of course, this was absolutely just a qu

Re: [VOTE] Release Apache Cassandra 4.0.7

+1 - - -- --- - - Jacek Lewandowski On Fri, Oct 21, 2022 at 11:18 AM Benjamin Lerer wrote: > +1 > > Le ven. 21 oct. 2022 à 10:27, Miklosovic, Stefan < > stefan.mikloso...@netapp.com> a écrit : > >> +1 >> >>

Re: [VOTE] Release Apache Cassandra 4.1-beta1

+1 - - -- --- - - Jacek Lewandowski On Fri, Sep 30, 2022 at 11:38 AM Andrés de la Peña wrote: > +1 > > On Fri, 30 Sept 2022 at 09:26, Benjamin Lerer wrote: > >> +1 >> >> Le ven. 30 sept. 2022 à 08:11, Miklosovic, Stefan < >>

  1   2   >