+1
From: Jon Haddad
Sent: Tuesday, February 7, 2023 4:55:51 PM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] CEP-21 Transactional Cluster Metadata
+1
On 2023/02/06 16:15:19 Sam Tunnicliffe wrote:
> Hi everyone,
>
> I would like to start a vote on this CEP.
>
Congratulations Josh!
From: Melissa Logan
Sent: Thursday, March 23, 2023 8:04:01 AM
To: dev
Subject: Re: Welcome our next PMC Chair Josh McKenzie
Josh, congratulations! Mick, thank you for all your efforts and support!
On Thu, Mar 23, 2023, 07:58 Joseph Lynch
m
Hi Jeremiah,
There are good reasons to not have these inside Cassandra. Consider the
following.
- Resources isolation. Having the said service running within the same JVM
may negatively impact Cassandra storage's performance. It could be more
beneficial to have them in Sidecar, which offers strong
A lot of great discussions!
On the sidecar front, especially what the role sidecar plays in terms of
this CEP, I feel there might be some confusion. Once the code is published,
we should have clarity.
Sidecar does not read sstables nor do any coordination for analytics
queries. It is local to the
+1
From: Jon Haddad
Sent: Thursday, May 4, 2023 3:31:52 PM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] CEP-28: Reading and Writing Cassandra Data with Spark Bulk
Analytics
+1.
Awesome work Doug! Great to see this moving forward.
On 2023/05/04 18:34:46 "C
+1
On Mon, May 15, 2023 at 3:13 PM Dinesh Joshi wrote:
> Proposing the test build of in-jvm dtest API 0.0.14 for release.
>
> Repository:
> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
>
> Candidate SHA:
>
> https://github.com/apache/cassandra-in-jvm-dtest-api/commit/ea4b
+1
From: Josh McKenzie
Sent: Thursday, May 25, 2023 5:37:02 PM
To: dev
Subject: Re: [VOTE] CEP-30 ANN Vector Search
+1
On Thu, May 25, 2023, at 8:33 PM, Jake Luciani wrote:
+1
On Thu, May 25, 2023 at 11:45 AM Jonathan Ellis
mailto:jbel...@gmail.com>> wrote:
Le
+1
From: David Capwell
Sent: Tuesday, June 13, 2023 8:37:10 AM
To: dev
Subject: Re: [VOTE] CEP-8 Datastax Drivers Donation
+1
On Jun 13, 2023, at 7:59 AM, Josh McKenzie wrote:
+1
On Tue, Jun 13, 2023, at 10:55 AM, Jeremiah Jordan wrote:
+1 nb
On Jun 13, 2023
+1
On Tue, Jun 27, 2023 at 1:50 PM Dinesh Joshi wrote:
> +1
>
>
> On Jun 27, 2023, at 1:23 PM, Josh McKenzie wrote:
>
>
> +1
>
> On Tue, Jun 27, 2023, at 1:17 PM, Shailaja Koppu wrote:
>
> Hi Team,
>
> (Starting a new thread for VOTE instead of reusing the DISCUSS thread, to
> follow usual pr
Thank you for fixing the build on ci-cassandra! I am glad that I can
contribute to the process :D
- Yifan
On Thu, Jul 20, 2023 at 4:00 PM Francisco Guerrero
wrote:
> Hi list,
>
> I wanted to bring some visibility into the Cassandra Sidecar CI health [1].
> It seems like it has been broken for q
+1
From: Dinesh Joshi
Sent: Friday, July 21, 2023 12:23:30 PM
To: dev
Subject: Re: [VOTE] CEP-34: mTLS based client and internode authenticators
+1
> On Jul 21, 2023, at 11:07 AM, Francisco Guerrero wrote:
>
> +1 (nb). This is a very valuable enhancement for th
+1
From: C. Scott Andreas
Sent: Saturday, August 19, 2023 9:51:16 AM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Release dtest-api 0.0.16
+1nb
On Aug 19, 2023, at 9:50 AM, Blake Eggleston wrote:
+1
On Aug 17, 2023, at 12:37 AM, Alex Petrov wrote:
+1
+1
From: David Capwell
Sent: Tuesday, October 3, 2023 9:45:02 AM
To: dev
Subject: Re: [VOTE] Accept java-driver
+1
On Oct 3, 2023, at 8:32 AM, Chris Lohfink wrote:
+1
On Tue, Oct 3, 2023 at 10:30 AM Jeff Jirsa
mailto:jji...@gmail.com>> wrote:
+1
On Mon, Oc
Hi,
I want to propose merging the patch in CASSANDRA-18941 to 4.0 and up to
trunk and hope we are all OK with it.
In CASSANDRA-18941, I am adding the capability to produce size-bounded
SSTables in CQLSSTableWriter for sorted data. It can greatly benefit
Cassandra Analytics (https://github.com/apa
Tables appropriately and efficiently.
>
> Doug
>
> On Oct 24, 2023, at 10:36 PM, guo Maxwell wrote:
>
> 😄
>
> Chris Lohfink 于2023年10月25日周三 05:02写道：
>
>> +1
>>
>> On Tue, Oct 24, 2023 at 11:24 AM Brandon Williams
>> wrote:
>>
>>> +1
>>>
+1
发件人: Sam Tunnicliffe
发送时间: Tuesday, November 28, 2023 2:43:51 AM
收件人: dev
主题: Re: [DISCUSS] Harry in-tree
Definite +1 to bringing harry-core in tree.
On 24 Nov 2023, at 15:43, Alex Petrov wrote:
Hi everyone,
With TCM landed, there will be way more Harry te
Congratulations! It is well deserved.
发件人: C. Scott Andreas
发送时间: Wednesday, November 29, 2023 2:56:34 AM
收件人: dev@cassandra.apache.org
主题: Re: Welcome Francisco Guerrero Hernandez as Cassandra Committer
Congratulations, Francisco!
- Scott
> On Nov 28, 2023, at
Congrats!
From: David Capwell
Sent: Monday, January 8, 2024 11:03:12 AM
To: dev
Subject: Re: Welcome Maxim Muzafarov as Cassandra Committer
Congrats!
On Jan 8, 2024, at 10:53 AM, Jacek Lewandowski
wrote:
Congratulations Maxim, well deserved, it's a pleasure t
Congrats all
From: Josh McKenzie
Sent: Wednesday, April 17, 2024 11:05:29 AM
To: dev
Subject: Re: Welcome Alexandre Dutra, Andrew Tolbert, Bret McGuire, Olivier
Michallat as Cassandra Committers
Congrats everyone and thanks for all the hard work to get things to
Hi Stefan,
Thanks for putting the FQL example! However, it seems to be incorrect. FQL
only records the _successful_ queries. The query at T4 fails, and it will
not be included in FQL log.
I do agree that changing guardrails on the fly can cause confusion when FQL
is enabled on the node. Operator s
I am voting against this for now.
There is an unaddressed gap between the functions. I do not believe there
is an equivalent replacement for the MAXWRITETIME function already, which
will disrupt its adopters.
MAXWRITETIME handles both single value columns and collections as input.
Meanwhile, COLL
Thank you for the service, Josh!
Congrats, Dinesh!
On Thu, Jun 20, 2024 at 11:32 AM Jean-Armel Luce wrote:
> Josh, thanks for the job
> Dinesh, congrats!!
>
> Le jeu. 20 juin 2024 à 19:42, David Capwell a écrit :
>
>> Congrats!
>>
>> On Jun 20, 2024, at 9:10 AM, Melissa Logan wrote:
>>
>> Josh
>
> - Alter and Drop constraints are as follows
> ALTER CONSTRAINT [name] CHECK new_condition DROP CONSTRAINT [name]
>
I think you mean the following syntax to modify existing constraints, since
constraints are part of the table definition.
ALTER TABLE [keyspace_name.]table_name ALTER CONSTRAINT [
+1 on CEP-42.
- Yifan
On Tue, Jul 2, 2024 at 5:17 AM Jon Haddad wrote:
> +1
>
> On Tue, Jul 2, 2024 at 5:06 AM wrote:
>
>> +1
>>
>>
>> On Jul 1, 2024, at 8:34 PM, Doug Rohrer wrote:
>>
>> +1 (nb) - Thanks for all of the suggestions and Bernardo for wrangling
>> the CEP into shape!
>>
>> Doug
Great addition in the tool set!
A separate repo would be better.
Grouping repos together only to be easier indexed does not seems to be a strong
supportive reason. Just my 2 cents.
- Yifan
- Yifan
From: Dinesh Joshi
Sent: Thursday, August 22, 2019 11:42 AM
To
+1 nb to the PR approach for reviewing.
And thanks David for initiating the discussion. I would like to put my 2
cents in it.
IMO, reviews comments are better associated with the changes, precisely to
the line level, if they are put in the PR rather than in the JIRA comments.
Discussions regard
CustomPayload should be used to provide customization via a custom query
handler (that is outside of Cassandra source).
Supporting custom timeout per query is a new feature. It is more clear to
assign a dedicated query flag. In V5, the available number of query flags
expanded from 8 (in V4 and prio
+1
From: Jasonstack Zhao Yang
Sent: Wednesday, April 8, 2020 9:04:51 AM
To: dev@cassandra.apache.org
Subject: Re: Keeping test-only changes out of CHANGES.txt
+1
On Thu, Apr 9, 2020, 00:04 Aleksey Yeshchenko
wrote:
> +1
>
> > On 8 Apr 2020, at 15:08, Mick Sem
+1
From: Sam Tunnicliffe
Sent: Wednesday, April 15, 2020 7:49:50 AM
To: dev@cassandra.apache.org
Subject: Re: Simplify voting rules for in-jvm-dtest-api releases
+1
> On 15 Apr 2020, at 14:35, Oleksandr Petrov wrote:
>
> Hi everyone,
>
> Apache release rules w
+1
Thank you Mick for the notification fix.
- Yifan
On May 16, 2020, 1:29 AM -0700, Mick Semb Wever , wrote:
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
+1 nb
From: Jon Haddad
Sent: Wednesday, June 17, 2020 2:13 PM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Project governance wiki doc
Yes, this is my understanding as well.
On Wed, Jun 17, 2020 at 2:10 PM Benedict Elliott Smith
wrote:
> I personally think
+1 nb
From: Scott Andreas
Sent: Saturday, June 20, 2020 11:00:15 AM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Project governance wiki doc (take 2)
+1 nb
> On Jun 20, 2020, at 9:37 AM, Joshua McKenzie wrote:
>
> +1 (binding / present / active)
>
> On Sat
+1 nb
From: Robert Stupp
Sent: Thursday, July 16, 2020 2:59:34 AM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta1
+1 (nb)
—
Robert Stupp
@snazy
> On 15. Jul 2020, at 20:07, Jasonstack Zhao Yang
> wrote:
>
> +1 (nb)
>
> On
+1
From: Caleb Rackliffe
Sent: Tuesday, September 1, 2020 12:08:50 PM
To: dev@cassandra.apache.org
Subject: Re: [DISCUSS] Change style guide to recommend use of @Override
+1
On Tue, Sep 1, 2020, 2:00 PM Jasonstack Zhao Yang
wrote:
> +1
>
> On Wed, 2 Sep 2020
+1
From: Joshua McKenzie
Sent: Wednesday, September 16, 2020 9:30:24 AM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Accept the Harry donation
+1
On Wed, Sep 16, 2020 at 11:22 AM, Aleksey Yeshchenko <
alek...@apple.com.invalid> wrote:
> +1
>
> On 16 Sep 2
+1 nb
From: Jon Meredith
Sent: Friday, September 25, 2020 8:39:31 AM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Release dtest-api 0.0.5
+1 (non-binding)
On Fri, Sep 25, 2020 at 9:16 AM Marcus Eriksson wrote:
>
> +1
>
> On 25 September 2020 at 17:13:36, C
+1 nb
From: Scott Andreas
Sent: Saturday, October 31, 2020 5:44:55 PM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta3
+1 nb
> On Oct 31, 2020, at 11:38 AM, Brandon Williams wrote:
>
> +1
>
> Signatures and checksums match, s
+1 nb
From: Marcus Eriksson
Sent: Monday, December 21, 2020 1:54:23 AM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Release Apache Cassandra 4.0-beta4
+1
On Fri, Dec 18, 2020 at 08:16:16PM +0100, Mick Semb Wever wrote:
> Proposing the test build of Cassandr
+1 nb.
We probably also want to set a milestone to get rid of the python2
compatible code completely, if we are going in the direction that drops
python2 support in 4.0 and retains the python2 compatible code. In 4.x or
5.0?
On Mon, Jan 25, 2021 at 9:24 AM Ekaterina Dimitrova
wrote:
> I support
+1 nb
On Fri, Jan 29, 2021 at 7:11 AM Aleksey Yeshchenko
wrote:
> +1
>
> > On 29 Jan 2021, at 14:31, Ekaterina Dimitrova
> wrote:
> >
> > +1(nb)
> >
> > On Fri, 29 Jan 2021 at 8:21, Oleksandr Petrov <
> oleksandr.pet...@gmail.com>
> > wrote:
> >
> >>> Proposing the test build of Cassandra 4.0-b
+1 nb
On Fri, Jan 29, 2021 at 7:11 AM Aleksey Yeschenko
wrote:
> +1
>
> > On 29 Jan 2021, at 14:30, Ekaterina Dimitrova
> wrote:
> >
> > +1(nb)
> >
> > On Fri, 29 Jan 2021 at 8:04, Mick Semb Wever wrote:
> >
> >>>
> >>> The vote will be open for 72 hours (longer if needed). Everyone who has
>
Congrats Joey!
From: Abe Ratnofsky
Sent: Wednesday, July 24, 2024 7:55:24 AM
To: dev@cassandra.apache.org
Subject: Re: Welcome Joey Lynch as Cassandra PMC member
Congratulations!
Hi everyone,
CASSANDRA-19800 is currently in the state of ready to be committed. Before
that, I want to propose backporting it to 4.0, 4.1 and 5.0.
The ability to notify CQLSSTableWriter user when new sstables are produced
is especially useful for Cassandra Analytics and other consumers. The API
;
>
>
>
> > On Jul 26, 2024, at 9:59 AM, Brandon Williams wrote:
> >
> > Given how low risk this is, I don't see an issue with backporting it
> > and I'm sure the usefulness outweighs what risk there is. +1 (5.0.1
> > though, not 5.0.0)
> >
Hi Jeremiah,
It is an interesting idea. As of now, I think it is too much of a risk (or
not feasible at all) to only use 5.0/trunk Cassandra-all dependency in
Cassandra Analytics, since it depends on other components in Cassandra.
- Yifan
It sounds like we are all good with backporting to 5.0.
Thank you all for the feedback.
- Yifan
On Fri, Jul 26, 2024 at 12:21 PM Jeff Jirsa wrote:
>
>
> On Jul 26, 2024, at 11:09 AM, Yifan Cai wrote:
>
>
> Thanks Jeff for restating the policy.
>
> According to t
x27;t thought deeply enough about this specific situation to have a
> well formed opinion, but figured calling out the above things is worth
> doing. This probably won't be the last time we look at our supported
> branches and have some pain we'd like to address based on the inco
Hi PMC team,
There are so far two +1 and one -1. Please vote if you want to. It is open
for another 12 hours.
4.1 is to be released. I would like to include the patch, if possible,
according to the vote result.
I recognize that patches to stable releases can be risky. When talking
about the trad
s before upgrading to
> future majors; I'm -1 on that.
>
> Thanks,
>
> – Scott
>
> On Jul 31, 2024, at 2:04 PM, Jon Haddad wrote:
>
>
> I'm kind of neutral on this, maybe -0. It's a small enough patch, but
> it's of limited value, given that Cassandra An
dad wrote:
>
>
> I'm kind of neutral on this, maybe -0. It's a small enough patch, but
> it's of limited value, given that Cassandra Analytics doesn't work with
> vnodes. That's the overwhelming majority of deployments. So I'm not really
> sure w
27;s.
Kind regards,
Yifan Cai
With WatcherService, when events are missed (which is to be expected), you
will still need to list the files. It seems to me that WatcherService
doesn't offer significant benefits in this case.
Regarding listing directory with a refresh flag, my concern is the
potential for abuse. End-users might/
Congrats Doug!
From: Jordan West
Sent: Friday, August 23, 2024 1:19:04 PM
To: dev@cassandra.apache.org
Subject: Re: Welcome Doug Rohrer as Cassandra Committer
Awesome! Congratulations Doug!
On Fri, Aug 23, 2024 at 12:17 Štefan Miklošovič
mailto:smikloso...@apac
The vote passes with 3 binding +1, 3 non binding, and no vetoes.
Thanks to everyone who was part of the discussion!
- Yifan
On Wed, Aug 7, 2024 at 3:57 PM Brandon Williams wrote:
> +1 for reasons stated in the discussion.
>
> Kind Regards,
> Brandon
>
> On Sun, Aug 4, 202
Congrats Jordan and Stefan!
From: Sumanth Pasupuleti
Sent: Friday, August 30, 2024 1:31:01 PM
To: dev@cassandra.apache.org
Subject: Re: Welcome Jordan West and Stefan Miklosovic as Cassandra PMC members!
Congratulations Jordan and Stefan!!!
On Fri, Aug 30, 2024
Congratulations Berenguer!
- Yifan
> On Mar 26, 2021, at 11:49 AM, Sumanth Pasupuleti
> wrote:
>
> Congratulations Berenguer!
-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: d
+1
On Mon, Mar 29, 2021 at 8:42 AM J. D. Jordan
wrote:
> +1 that deprecation schedule seems reasonable and a good thing to move to.
>
> > On Mar 29, 2021, at 10:23 AM, Benjamin Lerer wrote:
> >
> > The proposal sounds good to me too.
> >
> >> Le lun. 29 mars 2021 à 16:48, Brandon Williams a
>
+1 nb
On Mon, Mar 29, 2021 at 9:33 AM Aleksey Yeshchenko
wrote:
> +1
>
> > On 29 Mar 2021, at 14:05, Mick Semb Wever wrote:
> >
> > Proposing the test build of Cassandra 4.0-rc1 for release.
> >
> > sha1: 2facbc97ea215faef1735d9a3d5697162f61bc8c
> > Git:
> >
> https://gitbox.apache.org/repos/as
+1 to remove ant test parallelism and leverage container for it.
- Yifan
> On Apr 13, 2021, at 4:00 AM, Angelo Polo wrote:
>
> Docker doesn't run natively on FreeBSD (though work is underway to enable
> that). It's possible to run Docker Machine inside VirtualBox so maybe
> that's workable, ot
+1
On Wed, Apr 21, 2021 at 10:33 PM Berenguer Blasi
wrote:
> +1
>
> On 22/4/21 5:12, Blake Eggleston wrote:
> > +1
> >
> >> On Apr 21, 2021, at 2:25 PM, Scott Andreas
> wrote:
> >>
> >> +1nb, thank you!
> >>
> >>
> >> From: Ekaterina Dimitrova
> >> Sen
Congrats!
On Mon, May 3, 2021 at 1:23 PM Paulo Motta wrote:
> Congrats, Stefan! Happy to see you onboard! :)
>
> Em seg., 3 de mai. de 2021 às 17:17, Ben Bromhead
> escreveu:
>
> > Congrats mate!
> >
> > On Tue, May 4, 2021 at 4:20 AM Scott Andreas
> wrote:
> >
> > > Congratulations, Štefan!
>
Congrats Caleb!
> On May 14, 2021, at 6:56 AM, Joshua McKenzie wrote:
>
> Congrats Caleb!
>
>> On Fri, May 14, 2021 at 9:10 AM Brandon Williams wrote:
>>
>> Congrats Caleb! Well deserved.
>>
>>> On Fri, May 14, 2021, 8:03 AM Mick Semb Wever wrote:
>>>
>>> The PMC members are pleased to an
Hi,
In the current codebase, JMXTimer exposes its attributes in inconsistent
time units. The percentiles, Mean and DurationUnit attributes are using
micros. But the Values and RecentValues are based on nanos, since the
underlying Timer collects the time values in nanos.
The inconsistency leads to
>
> how much memory the Timers can currently use
Timer is currently backed by a DecayingEstimatedHistogramReservoir. [1]
Each DecayingEstimatedHistogramReservoir defaults to allocate [2]
1. *bucketOffsets*: a long array with the length of 164
2. *decayingBuckets*: a long array with the length of
+1
- Yifan
> On Jun 28, 2021, at 8:40 AM, Ekaterina Dimitrova
> wrote:
>
> +1 Thanks everyone!
>
>> On Mon, 28 Jun 2021 at 11:39, Aleksey Yeschenko wrote:
>>
>> +1
>>
On 28 Jun 2021, at 14:05, Gary Dusbabek wrote:
>>>
>>> +1; yay!
>>>
On Sun, Jun 27, 2021 at 11:02 AM Mick Se
, Jun 25, 2021 at 1:57 PM Yifan Cai wrote:
> how much memory the Timers can currently use
>
>
> Timer is currently backed by a DecayingEstimatedHistogramReservoir. [1]
>
> Each DecayingEstimatedHistogramReservoir defaults to allocate [2]
> 1. *bucketOffsets*: a long array w
+1 (nb)
On Fri, Jul 23, 2021 at 10:32 AM Jon Meredith wrote:
> +1 (nb)
>
> On Fri, Jul 23, 2021 at 10:22 AM Jake Luciani wrote:
>
> > +1
> >
> > On Fri, Jul 23, 2021 at 11:31 AM Blake Eggleston
> > wrote:
> >
> > > +1
> > >
> > > > On Jul 23, 2021, at 6:39 AM, Branimir Lambov <
> > > branimir.
Congrats Jon!
On Fri, Jul 30, 2021 at 8:48 AM Joshua McKenzie
wrote:
> Congratulations Jon!
>
>
> On Fri, Jul 30, 2021 at 10:35 AM Andrés de la Peña <
> a.penya.gar...@gmail.com>
> wrote:
>
> > Congratulations, Jon!
> >
> > On Fri, 30 Jul 2021 at 16:07, J. D. Jordan
> > wrote:
> >
> > > Congrat
>
> 2. Add retries to specific stages of coordination, such as prepare and
>validate. In order to do these retries we first need to know what the
state is for the participant which has yet to reply...
If I understand it correctly, does it mean retries only happen in the
coordinator and th
+1
- Yifan
> On Sep 1, 2021, at 7:57 AM, C. Scott Andreas wrote:
>
> +1nb
>
>> On Sep 1, 2021, at 6:54 AM, Jeff Jirsa wrote:
>>
>> +1
>>
>>
On Wed, Sep 1, 2021 at 4:54 AM Sam Tunnicliffe wrote:
>>>
>>> Proposing the test build of Cassandra 4.0.1 for release.
>>>
>>> sha1: 670911
+1
- Yifan
> On Sep 9, 2021, at 3:04 PM, Paulo Motta wrote:
>
> +1
>
>> On Thu, 9 Sep 2021 at 18:38 Ekaterina Dimitrova
>> wrote:
>>
>> +1
>>
>> On Thu, 9 Sep 2021 at 17:34, C. Scott Andreas
>> wrote:
>>
>>> +1nb
>>>
On Sep 9, 2021, at 2:03 PM, David Capwell
>>> wrote:
Congratulations Sumanth!
- Yifan
> On Nov 5, 2021, at 11:37 AM, Patrick McFadin wrote:
>
> Great to see this. Congrats Sumanth!
>
>> On Fri, Nov 5, 2021 at 11:34 AM Brandon Williams wrote:
>>
>> Congratulations Sumanth!
>>
>>> On Fri, Nov 5, 2021 at 1:17 PM Oleksandr Petrov
>>> wrote:
>>>
Would you like to elaborate on when to run the "canonical set of tests" and
when to run the others?
If my understanding is correct, we run the canonical set *before* merging,
and the runs triggered by the cassandra CI bot include the full set *after*
a commit is merged.
- Yifan
On Mon, Jan 10, 2
+1
On Tue, Jan 11, 2022 at 7:02 AM Andrés de la Peña
wrote:
> +1
>
> On Tue, 11 Jan 2022 at 13:45, Joshua McKenzie
> wrote:
>
>> If my understanding is correct, we run the canonical set *before* merging,
>>> and the runs triggered by the cassandra CI bot include the full set
>>> *after* a commi
>
> "All releases by default are expected to have a green test run on
> ci-cassandra Jenkins. In exceptional circumstances (security incidents,
> data loss, etc requiring hotfix), members with binding votes on a release
> may choose to approve a release with known failing tests."
+1 with the amen
>
> I think we should deprecate scripted UDFs now and drop them from the next
> major, but possibly provide hooks for people to write their own UDF
> "engines" and break out the current javascript implementation in to its own
> repository (but not ship it with Cassandra).
+1
Just want to clarify
+1 on the release
On Thu, Feb 10, 2022 at 7:23 AM Ekaterina Dimitrova
wrote:
> +0nb
> I am not sure I am getting enough information from our CI to vote for
> either +1 or -1. I was chasing CI issues two days, being worried did I
> break something with CCM change I introduced over the weekend as
Thank you Stefan for all the efforts!
Regarding the "merge strategy change", should we start a new thread?
I am +1 on adopting the merge button. It should work in the single branch
commit. Just the cross branch commit could be tricky.
- Yifan
Congratulations Aleksandr!
On Wed, Mar 16, 2022 at 7:34 AM Andrés de la Peña
wrote:
> Congrats, well deserved!
>
> On Wed, 16 Mar 2022 at 14:01, J. D. Jordan
> wrote:
>
>> Congratulations!
>>
>> On Mar 16, 2022, at 8:43 AM, Ekaterina Dimitrova
>> wrote:
>>
>>
>> Great news! Well deserved! Co
+1 to the guideline.
> > For the instance() / getInstance() methods - I know it is an additional
> effort, but on the other hand it has many advantages because you can
> replace the singleton for testing
>
> Again, do this as necessary. I think for public instances this is a fine
> recommendation
Congrats, Jacek!
From: C. Scott Andreas
Sent: Wednesday, July 6, 2022 8:26:26 AM
To: dev@cassandra.apache.org
Cc: dev@cassandra.apache.org
Subject: Re: Welcome Jacek Lewandowski as Cassandra committer
Congratulations, Jacek!
On Jul 6, 2022, at 7:38 AM, Mick Sem
e links and the ability to
>> automatically
>> refer to the JIRAs?
>>
>> On 2024/10/18 18:17:16 Yifan Cai wrote:
>> > Anyone know if there are any traps when renaming a JIRA project? Since
>> we
>> > are talking about change CASSANDRASC to CASS-SIDECAR.
characters.
>> >>>
>> >>> —
>> >>> Jon Haddad
>> >>> Rustyrazorblade Consulting
>> >>> rustyrazorblade.com
>> >>>
>> >>>
>> >>> On Thu, Oct 17, 2024 at 1:57 PM Štefan Miklošovič <
well 于2024年10月16日 周三上午9:55写道：
>
>> Hi yifan,
>> Thanks for bringing this up. The SELECT permission on the original table
>> is needed. Mysql and PG all have mentioned this, and I also specifically
>> noticed this in my code.
>>
>> I probably missed this i
+1 nb
From: Brandon Williams
Sent: Thursday, October 17, 2024 11:47:13 AM
To: dev@cassandra.apache.org
Subject: Re: [VOTE] CEP-44: Kafka integration for Cassandra CDC using Sidecar
+1
Kind Regards,
Brandon
On Thu, Oct 17, 2024 at 1:08 PM James Berragan wrote:
>>> <https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-43++Apache+Cassandra+CREATE+TABLE++LIKE>
>>> .
>>>
>>>
>>> Patrick McFadin 于2024年10月17日周四 06:43写道：
>>>
>>>> +1 That makes much more sense in my experience.
>>>&
think we just need to ask infra to create the jira instances, but
>> I
>> >>> > guess we need to have some kind of consistent naming scheme to help
>> >>> > identify them?
>> >>> >
>> >>> > Kind Regards,
yep. CASSANALYTICS sounds good to me. +1
On Thu, Oct 17, 2024 at 1:45 PM Francisco Guerrero
wrote:
> > Can we include Cassandra Analytics to the infra ticket? I am looking
> > forward to jira project name suggestions for it...
>
> How about CASSANALYTICS ?
>
> On 2024/
+1 on all the points raised by Mick. Please let me know if there is
anything I can help with.
- Yifan
On Wed, Oct 2, 2024 at 8:13 AM Josh McKenzie wrote:
> - Qbot notifications in #cassandra-dev and #cassandra-noise , as well as
> in any subproject channels
> - some cadence of dev@ ML updates,
Thanks for working on this!
Another bikeshed I noticed is the project logo.
Currently, all of them share the same one as Sidecar. The subprojects can
be styled up. :p
- Yifan
On Wed, Oct 23, 2024 at 9:46 AM Brandon Williams wrote:
> https://issues.apache.org/jira/projects/CASSPYTHON/
> https
gt;
>> I'm going to cap this thread. Vote passes with no binding -1s.
>>
>> On Tue, Jul 2, 2024 at 2:25 PM Jordan West wrote:
>>
>>> +1
>>>
>>> On Tue, Jul 2, 2024 at 12:15 Francisco Guerrero
>>> wrote:
>>>
>>>>
I am in favor of *disallowing* the `var` keyword.
It does not provide a good readability, especially in the environments w/o
type inference, e.g. text editor or github site.
It could introduce performance degradation without being noticed. Consider
the following code for example,
Set allNames()
t;>> Now at this point I think we can continue the voting for CEP-43 as
>>>>>> all the feedback in the discussion thread seems to be addressed.
>>>>>>
>>>>>> Proposal: CEP43-CREATE TABLE LIKE
>>>>>> <https://cwiki.ap
I support the idea of having separate Jira projects. Based on my experience
with both shared namespaces (like Cassandra and Analytics) and dedicated
namespaces (like Sidecar), I've seen the drawbacks of grouping all
subproject tickets under a single project, i.e. Cassandra.
When tickets are consol
e exclusion. This is an interesting problem. If
>>> somebody wants these two to be constrained and checked then I guess the
>>> solution would be to have them both in a tuple instead of in two different
>>> columns. So we do not need to support this cross-columns feature. Howe
to be added to the reserved keywords. I would propose a new
iteration.
ALTER TABLE ks.table ALTER [IF EXISTS] DROP CONSTRAINTS;
Thank you for providing additional examples to illustrate the unnecessity
of constraint names.
- Yifan
On Fri, Oct 25, 2024 at 11:16 AM Yifan Cai wrote:
> Hi
For further discussions, should we use the discussion thread? This thread
is for voting.
- Yifan
On Tue, Oct 15, 2024 at 3:31 PM Bernardo Botella <
conta...@bernardobotella.com> wrote:
> Hi Guo,
>
> Do you think it would make sense to add a fourth keyword to add after the
> WITH for Constraints?
Thanks for creating the CEP! I think it is missing Bernardo's comment on
"the need for read permissions on the source table".
CreateTableStatement does not check the permissions outside of the
enclosing keyspace. Having the SELECT permission on the original table is a
requirement for CREATE TABLE
H would be equivalent.
> But, for strings, they are difference. For the string “foo”, LENGTH would
> be 3, but size would be bigger than 3 (depending on the actual encoding
> used).
>
>
> On Feb 8, 2025, at 7:58 PM, Yifan Cai wrote:
>
> It makes sense to me to have both guardr
While LOOSE_NOT_NULL might improve the clarity a bit, what is the value of such
constraint provides to users? It still permits null. Meanwhile, it is easier to
check the nullness of the bound values on the application side.
IMO, what benefits users is a way to ensure no null value can exist for t
1 - 100 of 118 matches
Mail list logo
