Re: [VOTE] Release dtest-api 0.0.12

+1 On Mon 24. Jan 2022 at 13:57, Andrés de la Peña wrote: > +1 > > On Mon, 24 Jan 2022 at 12:29, Brandon Williams wrote: > >> +1 >> >> On Thu, Jan 13, 2022 at 12:17 PM Mick Semb Wever wrote: >> > >> > Proposing the test build of in-jvm dtest API 0.0.12 for release. >> > >> > Repository: >> >

Welcome Sumanth Pasupuleti as Apache Cassandra Committer

The PMC members are pleased to announce that Sumanth Pasupuleti has recently accepted the invitation to become committer. Sumanth, thank you for all your contributions to the project over the years. Congratulations and welcome! The Apache Cassandra PMC members

Re: [DISCUSS] Releasable trunk and quality

I'll merge 16262 and the Harry blog-post that accompanies it shortly. Having 16262 merged will significantly reduce the amount of resistance one has to overcome in order to write a fuzz test. But this, of course, only covers short/small/unit-test-like tests. For longer running tests, I guess for

Re: Paging in bytes (CASSANDRA-11745)

I personally think this change should be small enough to just be done via jira without introducing a CEP. But since paging generally has seen some problems, it'd be good to understand the design before flushing it out in code. One of the ways where we probably should be considerate is the paging

Re: Save CircleCI resources with optional test jobs

onally support the current workflow and approval > required > > > but if it is not acceptable to others and skipping the build approval > > click > > > is what others would prefer, I will open a ticket to restore that part. > > > Please let me know and one more time, apol

Re: Save CircleCI resources with optional test jobs

I thought this discussion was still ongoing, but it looks like CASSANDRA-16882 is now committed. Could you give some context on why at least compilation is not done on every commit now? On Fri, Oct 8, 2021 at 4:12 PM Oleksandr Petrov wrote: > I personally rarely push tickets/post a pa

Re: [VOTE] CEP-15: General Purpose Transactions

1. +1 2. +1 3. +1 On Thu, Oct 14, 2021 at 6:31 PM bened...@apache.org wrote: > Hi everyone, > > I would like to start a vote on this CEP, split into three sub-decisions, > as discussion has been circular for some time. > > 1. Do you support adopting this CEP? > 2. Do you support the transaction

Re: Tradeoffs for Cassandra transaction management

I realise this is not contributing to this discussion, but this email is very difficult to read because it seems like something has happened with formatting. For me it gets displayed as a single paragraph with no line breaks. There seems to be some overlap between the image uploaded to imgur and

Re: [DISCUSS] CEP-15: General Purpose Transactions

> I support this proposal. From what I can understand, this proposal moves us towards having the building blocks we need to correctly deliver some of the most often requested features in Cassandra. Same here. I also support this proposal and believe it opens up many new opportunities (while not

Re: Save CircleCI resources with optional test jobs

I personally rarely push tickets/post a patch in an raw state, but since I almost always have to approve jobs when it gets close to commit, I don't mind also confirming utest runs. I'd say it'd be good to run at very least a compilation step on every commit. I think it's fine if dtests/utests/jvm

Re: [VOTE] Release dtest-api 0.0.10

wrote: > >> > >> +1 > >> > >>> On Tue, Oct 5, 2021 at 11:47 AM Oleksandr Petrov > >>> wrote: > >>> > >>> Proposing the test build of in-jvm dtest API 0.0.10 for release. > >>> > >>> Repository: > &g

[VOTE] Release dtest-api 0.0.10

Proposing the test build of in-jvm dtest API 0.0.10 for release. Repository: https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.10 Candidate SHA: https://github.com/apache/cassandra-in-jvm-dtest-api/commit/2139b4c85e319b17afbdea2f653152d1e1895fc6

Re: [VOTE] Release Apache Cassandra 4.0.0 (third time is the charm)

+1 On Fri, Jul 23, 2021 at 7:40 AM Jeff Jirsa wrote: > +1 > > > On Jul 22, 2021, at 3:41 PM, Brandon Williams < > brandonwilli...@apache.org> wrote: > > > > I am proposing the test build of Cassandra 4.0.0 for release. > > > > sha1: 902b4d31772eaa84f05ffdc1e4f4b7a66d5b17e6 > > Git: >

Re: [VOTE] Release dtest-api 0.0.8

+1 On Fri, Jul 9, 2021 at 12:29 PM Mick Semb Wever wrote: > Proposing the test build of in-jvm dtest API 0.0.8 for release. > > Repository: > > https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.8 > > Candidate SHA: > >

Re: [DISCUSSION] Should we mark DROP COMPACT STORAGE as experimental

Thank you for bringing this subject up. > not ready for production use unless users fully understand what they are doing. Thing is, there's no easy way around dropping compact storage. At the moment of writing of 10857, we have collectively decided that we'll document that the new columns are

Re: Pushing CASSANDRA-16262 out of 4.0-rc

In the absence of a fuzz testing tool I would probably support excluding this ticket from GA, but speaking from recent experience it feels to me that fixing bugs is blocking us from further fuzz testing more than fuzz testing is blocking us from releases. In other words, you run a fuzz test for a

Re: [VOTE] Release Apache Cassandra 3.11.10

This vote has passed, after 3 days, with seven binding +1s, three non-binding +1s, and no -1s. On Mon, Feb 1, 2021 at 2:57 PM Brandon Williams wrote: > +1 > > On Fri, Jan 29, 2021, 6:50 AM Oleksandr Petrov > > wrote: > > > Proposing the test build of Cassandra 3.11.10 f

Re: [VOTE] Release Apache Cassandra 3.0.24

This vote has passed, after 3 days, with seven binding +1s, three non-binding +1s, and no -1s. On Mon, Feb 1, 2021 at 2:57 PM Brandon Williams wrote: > +1 > > On Fri, Jan 29, 2021, 6:48 AM Oleksandr Petrov > > wrote: > > > Proposing the test build of Cassand

[RELEASE] Apache Cassandra 3.0.24 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.0.24. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

[RELEASE] Apache Cassandra 3.11.10 released

The Cassandra team is pleased to announce the release of Apache Cassandra version 3.11.10. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://cassandra.apache.org/ Downloads of source

Re: [VOTE] Release Apache Cassandra 3.0.24

> Proposing the test build of Cassandra 4.0-beta4 for release. Correction: test build of 3.0.24. The rest looks right. On Fri, Jan 29, 2021 at 1:48 PM Oleksandr Petrov wrote: > Proposing the test build of Cassandra 4.0-beta4 for release. > > sha1: 6748ecd63cae047b5b0e8c316508825295

[VOTE] Release Apache Cassandra 3.11.10

Proposing the test build of Cassandra 3.11.10 for release. sha1: 181a4969290f1c756089b2993a638fe403bc1314 Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.10-tentative Maven Artifacts:

[VOTE] Release Apache Cassandra 3.0.24

Proposing the test build of Cassandra 4.0-beta4 for release. sha1: 6748ecd63cae047b5b0e8c3165088252954e9d5f Git: https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.24-tentative Maven Artifacts:

Re: [DISCUSS] Bringing protocol v5 out of beta and dropping support from 3.11.x

> Nit-picking, "beta" isn't sounding like the most accurate classifier here. It sounds to me more like it is "in development", i.e. 'dev', rather than beta. I agree that `dev` rather than `beta` is a better classifier. We probably should rename it at least internally and in the spec. That might

Re: [DISCUSS] Bringing protocol v5 out of beta and dropping support from 3.11.x

I wanted to point out that beta version of the protocol was created [1] only for development purposes: > This is primarily useful for driver authors to start work against a new protocol version when the work on that spans multiple releases. Users would not generally be expected to utilize this

[VOTE] Release dtest-api 0.0.7

Proposing the test build of in-jvm dtest API 0.0.7 for release. Repository:https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.7 Candidate SHA:https://github.com/apache/cassandra-in-jvm-dtest-api/commit/d5174b1f44b7d9cb919d4975b4d437041273c09c tagged

Re: Minimal 4.0 COMPACT STORAGE backport

; bug. > > > I truly believe it is too late in the release to document changed > > behavior. > > > I think this contradicts with the project’s promise for no breaking > > > changes. This should have been documented in alpha. > > > Best regards, > > > Ekater

Minimal 4.0 COMPACT STORAGE backport

Since this is an important subject, I thought it also makes sense to start a mailing list thread. You may know that in 4.0 there was a plan to drop compact storage and related code. However, there are several behavioural changes related to compact storage, and difference in visible behaviour

Re: [VOTE] Release dtest-api 0.0.6

With 7 +1 votes, and no -1s, the vote passes. On Fri, Oct 9, 2020 at 1:12 AM Nate McCall wrote: > +1 > > On Thu, Oct 8, 2020 at 9:20 PM Oleksandr Petrov < > oleksandr.pet...@gmail.com> > wrote: > > > Proposing the test build of in-jvm dtest API 0.0.6 f

[VOTE] Release dtest-api 0.0.6

Proposing the test build of in-jvm dtest API 0.0.6 for release. Repository: https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.6 Candidate SHA: https://github.com/apache/cassandra-in-jvm-dtest-api/commit/9efeb731b6ff4036fa822b0282b27d273975cd6fTT

Re: [VOTE] Release dtest-api 0.0.5

0.0.5 is now released: https://repository.apache.org/service/local/repositories/releases/content/org/apache/cassandra/dtest-api/0.0.5/ On Thu, Oct 1, 2020 at 8:01 AM Oleksandr Petrov wrote: > With 8 +1 votes, and no -1s, the vote passes. > > > On Fri, Sep 25, 2020 at 5:50 PM Yifa

Re: [VOTE] Release dtest-api 0.0.5

25, 2020 at 10:11 AM Caleb Rackliffe > > > wrote: > > > > > > > +1 > > > > > > > > On Fri, Sep 25, 2020 at 10:08 AM Brandon Williams > > > > wrote: > > > > > > > > > +1 > > > > > > >

[VOTE] Release dtest-api 0.0.5

Proposing the test build of in-jvm dtest API 0.0.5 for release. Repository: https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.5 Candidate SHA: https://github.com/apache/cassandra-in-jvm-dtest-api/commit/f900334d2f61f0b10640ba7ae15958f26df72d92 tagged

Re: Creating a branch for 5.0 …?

> So, here's what I've done, in an effort to make a space for both of these groups to operate: the exact same thing we've done for every release in the past. I created a branch for the 4.0 release. I agree that everyone is free to work on whatever they want, but it seems like having a 4.next

Re: [DISCUSS] CEP-7 Storage Attached Index

t would involve some > > bits of > > > information DataStax might not be ready to share? > > > > > > On Wed, Sep 23, 2020 at 11:00 AM Jeremiah D Jordan < > jeremiah.jordan@ > > > gmail.com> wrote: > > > > > > S

Re: [DISCUSS] CEP-7 Storage Attached Index

it. > > > > On Sep 23, 2020, at 10:34 AM, Oleksandr Petrov < > oleksandr.pet...@gmail.com> wrote: > > > > Short question: looking forward, how are we going to maintain three 2i > > implementations: SASI, SAI, and 2i? > > > > Another thing I think

Re: [DISCUSS] CEP-7 Storage Attached Index

Short question: looking forward, how are we going to maintain three 2i implementations: SASI, SAI, and 2i? Another thing I think this CEP is missing is rationale and motivation about why trie-based indexes were chosen over, say, B-Tree. We did have a short discussion about this on Slack, but both

Re: [VOTE] Accept the Harry donation

+1 On Thu, Sep 17, 2020 at 6:28 PM Blake Eggleston wrote: > +1 > > > On Sep 16, 2020, at 2:45 AM, Mick Semb Wever wrote: > > > > This vote is about officially accepting the Harry donation from Alex > Petrov > > and Benedict Elliott Smith, that was worked on in CASSANDRA-15348. > > > > The

Re: [DISCUSS] CEP-8 Drivers Donation

I've tried to find this information in the document above, but couldn't find an explicit mention of it, possibly because it's implied. If we take java-driver as an example, is this CEP proposing to contribute all branches (3.x and 4.x) or only the latest one? Thank you, -- Alex On Wed, Jul 29,

[VOTE] Release dtest-api 0.0.4

Proposing the test build of in-jvm dtest API 0.0.4 for release. Repository: https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.4 Candidate SHA: https://github.com/apache/cassandra-in-jvm-dtest-api/commit/b481c85f9ce49e17b47765800ca5c2b396b1fa73 tagged

Re: [VOTE] Release dtest-api 0.0.3

With 5 +1 (including my own) and no -1, the vote passes. On Fri, Jul 3, 2020 at 7:37 PM Jon Haddad wrote: > +1 > > On Fri, Jul 3, 2020 at 7:03 AM Brandon Williams wrote: > > > +1 > > > > On Fri, Jul 3, 2020, 4:57 AM Oleksandr Petrov < > o

[VOTE] Release dtest-api 0.0.3

Proposing the test build of in-jvm dtest API 0.0.3 for release. Repository: https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.3 Candidate SHA: https://github.com/apache/cassandra-in-jvm-dtest-api/commit/3f01a1743a0dcc9d0b054e12bd53f808dd1adc49 tagged

Re: List of serious issues fixed in 3.0.x

Wanted to add some that I remembered: * https://issues.apache.org/jira/browse/CASSANDRA-12811 - data resurrection, but was marked as normal because was discovered with a test. Should've marked it as critical. * https://issues.apache.org/jira/browse/CASSANDRA-12956 - data loss (commit log

Re: Scope of CASSANDRA-14557 (Default and Minimum RF)

I think it is reasonable that system keyspaces would get initialized with a default replication factor, assuming ones that were already initalized would remain intact (however, this should be the same for user-created keyspaces). Assuming it doesn't change the current behaviour, and default and

Re: Calling for release managers (Committers and PMC)

Not sure if I’m too late to the game but you can count me in, too! On Tue 12. May 2020 at 18:42, Mick Semb Wever wrote: > Thanks everyone! > > I've created a confluence page for the onboarding process. > > https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Managers+Onboarding > >

Re: [VOTE] Release dtest-api 0.0.2

The vote passed with 4 +1 votes (including mine) and 0 -1s. On Thu, Apr 30, 2020 at 10:51 AM Marcus Eriksson wrote: > +1 > > > On 29 April 2020 at 17:08:57, David Capwell (dcapw...@apple.com.invalid) > wrote: > > +1. > > Checked integration with Cassandra and upgrade > > > > Sent from my iPhone

[VOTE] Release dtest-api 0.0.2

Proposing the test build of in-jvm dtest API 0.0.2 for release. Repository: https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git;a=shortlog;h=refs/tags/0.0.2 Candidate SHA: https://github.com/apache/cassandra-in-jvm-dtest-api/commit/6d7679a349d7500554d6fbdcdd3f82030805b240 tagged

Re: Simplify voting rules for in-jvm-dtest-api releases

cassandra.a.o somewhere (developer and > releases > >> pages maybe?). Nothing exhaustive, just 'we do X with Y'. > >> > >> > >> On Thu, Apr 16, 2020 at 11:03 PM Oleksandr Petrov < > >> oleksandr.pet...@gmail.com> wrote: > >> > >>> I'

Re: Simplify voting rules for in-jvm-dtest-api releases

give the ASF a > reasonable > > degree of assurance for indemnification. However, we might have a fair > > degree of leeway so long as we do 'vote', it's test scope (as Mick > pointed > > out) and the process for such is published somewhere? > > > > Cheers, >

Re: Simplify voting rules for in-jvm-dtest-api releases

The most important thing for the purposes of what we’re trying to achieve is to have a unique non overridable version. In principle, a unique tag with release timestamp should be enough, as long as we can uniquely reference it. However, even then, I’d say release frequency (establishing “base”)

Re: [VOTE] Release Apache Cassandra 4.0-alpha4

+1 On Wed, Apr 15, 2020 at 10:21 AM Benjamin Lerer wrote: > +1 > > > > On Tue, Apr 14, 2020 at 5:50 PM Blake Eggleston > wrote: > > > +1 > > > > > On Apr 14, 2020, at 5:09 AM, e.dimitr...@gmail.com wrote: > > > > > > I also can’t see them. I think it matters to which interface is the > > link.

Simplify voting rules for in-jvm-dtest-api releases

Hi everyone, Apache release rules were made for first-class projects. I would like to propose simplifying voting rules for in-jvm-dtest-api project [1]. A bit of background: in-jvm-dtest-api is a project that is used by all active Cassandra branches (2.2, 3.0, 3.11, and trunk) to unify

Re: server side describe

> My understanding is that a majority of people ended up in favor of a DESCRIBE approach. Robert made a patch for that approach (according to his comment it was discussed with Chris beforehand). This sounds like just a switch of API (in other words, you use the same string generation, but return

Re: [VOTE] Release dtest-api 0.0.1

Just to make sure to mention it explicitly: I'm holding off the release itself till https://issues.apache.org/jira/browse/CASSANDRA-15652 is merged. On Thu, Mar 26, 2020 at 11:43 AM Oleksandr Petrov < oleksandr.pet...@gmail.com> wrote: > The vote passed with 4 +1 votes (including mine)

Re: [VOTE] Release dtest-api 0.0.1

The vote passed with 4 +1 votes (including mine) and 0 -1s. Thank you, -- Alex On Thu, Mar 26, 2020 at 10:42 AM Sam Tunnicliffe wrote: > +1 > > Sam > > > On 23 Mar 2020, at 09:36, Oleksandr Petrov > wrote: > > > > Thanks to everyone who participated in the p

Re: CircleCI config change?

; always needed. Intermediate pushes just to save pieces of work do not > require immediate CI run. That was my point. > Ekaterina > > Sent from my iPhone > > > On 25 Mar 2020, at 9:07, Oleksandr Petrov > wrote: > > > > I recently had to fix at least two problems

Re: CircleCI config change?

I recently had to fix at least two problems that could've been prevented by running tests and checks that are about to be turned off by default ([1] and [2]). I'd like to point out that this has happened while checks were theoretically enabled, and both problems could've been prevented. This

[VOTE] Release dtest-api 0.0.1

Thanks to everyone who participated in the previous vote, I appreciate your feedback. @Mick, thank you for sending a patch and helping to figure out the release procedure and specifics. Proposing the test build of in-jvm dtest API 0.0.1 for release. Repository:

Re: [VOTE] Release dtest-api 0.0.3

https://repository.apache.org/content/repositories/orgapachecassandra-1199/org/apache/cassandra/dtest-api/0.0.1/ I've left sources artifact, but added md5 and sha checksums. Thank you for helping out with this, -- Alex On Sat, Mar 21, 2020 at 10:45 AM Oleksandr Petrov < oleksandr.pet...@gmail.com> wrot

Re: [VOTE] Release dtest-api 0.0.3

Thanks for bringing these up! > this fixes everything but the signing key used issue https://github.com/apache/cassandra-in-jvm-dtest-api/pull/2 Great, I'll just merge this together with my branch to master to have a ref. Thank you for taking time to resolve these. > * Source artifacts does

Protocol-impacting (internode and client) changes for 4.0

Hi, During NGCC/ACNA19 we've had quite a few conversations around the 4.0 release. Many (minor) features and changes suggested during that time are possible to implement in 4.next without any problem. However, some changes that seem to be very important for the community, which got mentioned in

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

Maybe a bit off-topic: Before we cut a release, we should make sure we take care of beta protocol [1], include released driver versions [2] and remove compact storage remainders [3]. Third one is optional, but I'd argue we should do it sooner rather than later. [1]

Re: Stabilising Internode Messaging in 4.0

Sorry to pick only a few points to address, but I think these are ones where I can contribute productively to the discussion. > In principle, I agree with the technical improvements you mention (backpressure / checksumming / etc). These things should be there. Are they a hard requirement for 4.0?

Re: Stabilising Internode Messaging in 4.0

To be fair, even though the patch totals to 20K LoC, the core of the patch is within reasonable bounds (around net.async.*). There are many changes because of the code that got moved around. Some parts changes look large because Java is quite a verbose language (e.g., metric tables).

Re: [VOTE] Change Jira Workflow

+1 On Mon, Dec 17, 2018 at 7:12 PM Nate McCall wrote: > > On Tue, Dec 18, 2018 at 4:19 AM Benedict Elliott Smith > wrote: > > > > I propose these changes > > * > > to the Jira Workflow for the project. The vote

Reviewer for CASSANDRA-14055

Hi everyone, I still couldn't find enough time to review the https://issues.apache.org/jira/browse/CASSANDRA-14055 for which I'm deeply sorry. It's a SASI issue related to index redistribution. Unfortunately, this week doesn't look very promising in terms of time as well, so I'm making a call

Compact Storage and SuperColumn Tables in 4.0/trunk

As you may know, SuperColumn Tables did not work in 3.x the way they worked in 2.x. In order to provide everyone with a reasonable upgrade path, we've been working on CASSANDRA-12373[1], that brings in support for SuperColumn tables as close to 2.x as possible. The patch is planned to land

CASSANDRA-13004 FAQ

Hi everyone, There were many people asking similar questions about the CASSANDRA-13004. It might be that the issue itself and release notes are somewhat hard to grasp or might sound ambiguous, so here's a bit more elaborate explanation what 13004 means in terms of the upgrade process, how it

Re: 3.10 release status: blocked on dtest

#13025 was updated yesterday. It just needs some feedback, but we know what the problem is there. On Wed, Jan 4, 2017 at 5:32 PM Michael Shuler wrote: > On 12/20/2016 03:48 PM, Michael Shuler wrote: > > Current release blockers in JIRA on the cassandra-3.11 branch are: >

Re: CASSANDRA-8596

I would recommend several things that could help this (and probably many other patches that accidentally went under radar) to get accepted. It's hard to keep an enormous amount of issues in memory, so we try to rely on simple rules that help everyone to see current status and understand what to do

Segfaults in Unit Test Results on CI

Hi everyone, Wanted to ask everyone to take extra care when you see error messages such as: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit. in your unit test reports on cassci. When you see such a failure, please always check

Re: [VOTE] Release Apache Cassandra 3.10 (Take 3)

>From just a quick glance, I can say at least some of the tests are either PA or are getting there: For example: http://cassci.datastax.com/job/cassandra-3.X_novnode_dtest/lastCompletedBuild/testReport/paging_test/TestPagingData/test_paging_with_filtering_on_partition_key/ Should be fixed by

Re: [VOTE] Release Apache Cassandra 3.10 (Take 2)

-1 Sorry but I have to -1 that one, with the following explanation One of the features in 3.10 breaks SASI in quite a significant way. The issue was introduced in #11990 [1] and described in #12877 [2]. If there are more than 8 items in partition that have same index value, index file will get

Re: Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)

Recently there was another discussion on documentation and comments [1] On one hand, documentation and comments will help newcomers to familiarise themselves with the codebase. On the other - one may get up to speed by reading the code and adding some docs. Such things may require less oversight

Re: Cleanup after yourselves please

en (or at least > refactored) after your work? Couldn't we use /* */ comments instead of > every single line one by one? Given we use source control couldn't we > remove the dead code and get it from the revision history if we need it in > the future? > > > On Oct 18

Re: Cleanup after yourselves please

I'm currently working on actually making Super Columns work in CQL context. Currently they do not really work[1]. It's not a very small piece of work. It was in the pipeline for some time, although there most likely were more important things that had to be worked on. I understand your

Re: Failing tests 2016-09-28

-- > AY > > On 28 September 2016 at 17:48:27, Philip Thompson ( > philip.thomp...@datastax.com) wrote: > > That ticket was only supposed to be committed to 3.10 and 3.0.x. Was it > accidentally also merged into 3.9? > > On Wed, Sep 28, 2016 at 12:40 PM, Oleksandr

Re: Failing tests 2016-09-28

accidentally also merged into 3.9? > > On Wed, Sep 28, 2016 at 12:40 PM, Oleksandr Petrov < > oleksandr.pet...@gmail.com> wrote: > > > LWTTester issues are leftovers from the bad merge in > > https://github.com/riptano/cassandra-dtest/pull/1214 > > > > I've

Re: Failing tests 2016-09-28

LWTTester issues are leftovers from the bad merge in https://github.com/riptano/cassandra-dtest/pull/1214 I've rebased and currently re-running tests. On Wed, Sep 28, 2016 at 6:23 PM Philip Thompson < philip.thomp...@datastax.com> wrote: > Hi All, > > cassandra-3.9: >

Re: Failing tests 2016-09-15

I've been able to reproduce both SASI statics (saved sstables, going to take a closer look) and 11031 tests with novnode (looks like paging problem that was not appearing when all parts of partition key were locked), will create a Jira ticket today. On Fri, Sep 16, 2016 at 7:24 AM Joel Knighton

Re: Failing tests 2016-09-14

e could extract all the filtering tests > into a new TestClass: FilteringTest or SelectWithFilteringTest. > > On Thu, Sep 15, 2016 at 8:34 AM, Oleksandr Petrov < > oleksandr.pet...@gmail.com> wrote: > > > > CASSANDRA-11031 > > > > Yes, sorry for dela

Re: Failing tests 2016-09-14

> CASSANDRA-11031 Yes, sorry for delay with #11031 dtests. I've ran updated dtests yesterday and they were clean to merge. I just wanted to make sure someone else takes a quick glance. By now they're merged, so hopefully today it's going to be better. As regards environmental timeouts, it looks

Re: Documentation on a new CQL feature of 3.6

As far as I understand this wording, it's correct. Prior to 3.6 *filtering* was not allowed on clustering columns. It was allowed to do non-filtering queries involving clustering columns, although you could not specify any clustering column (or combine multiple range queries). Now it is allowed.

Re: How to debug a unit test?

I'm not entirely sure how to debug in terminal. But you can set break points and debug in eclipse and IntelliJ without a problem. I strongly recommend reading the contributing guide: https://wiki.apache.org/cassandra/HowToContribute On Fri, 20 May 2016 at 03:18, Mahdi Mohammadi

Re: Error running 'ant test'

t > > org.apache.cassandra.index.internal.CassandraIndexTest.indexOnNonFrozenMapValuesWithReplaceOperation(CassandraIndexTest.java:212)* > *[junit]* > *[junit]* > *[junit] Test org.apache.cassandra.index.internal.CassandraIndexTest > FAILED* > > > > > Best Regards > > On Thu, May 19, 2016 at

Re: How cassandra ensures consistency when adding or removing a node?

I think that this article [1] covers most of the concepts (see key concepts) quite well. I am not aware of any article that explains the whole process, though. Briefly, there are several processes/concepts that are somewhat related to that subject: token ownership, replica, coordinator and

Re: Error running 'ant test'

I just tried it locally, `ant clean && ant test -Dtest.name=TopKSamplerTest` works just fine (tried the other test, too). What's your JDK version? I can't see anything obvious that is wrong. If the branch is up-to-date, it usually has to build. On Thu, May 19, 2016 at 5:12 AM Mahdi Mohammadi

Re: [Proposal] Mandatory comments

I think that Netty is a good example of comments, at least for me they often were helpful, both from perspective of working on the code and from user perspective (when something seems to be working not as expected, you can usually find out reasons for it from the code in a straightforward way). I