Re: [Proposal] add pull request template

I like auto linking, definitely a handy feature. I am not sure about the content of the pull request description. I would include what that PR is actually for / why it is necessary to merge it and into what branches a contributor expects that PR to be merged in. However, this might be omitted if

[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] Moving deb/rpm repositories from downloads.apache.org to apache.jfrog.io

Thanks Bowen, Jeremiah, Brandon, Erick. Without any further questions or objections, my plan is to move ahead with these changes tomorrow. On Fri, 12 Aug 2022 at 09:10, Erick Ramirez wrote: > +1 from me. I think this will make it easier for new users. We just need > to document the procedure

Re: [Proposal] add pull request template

If there is consensus that the PR template is a good idea, I'll create a branch and we can wrangle the words. I think the pull request generally is against a specific branch but having the branch listed in the template is not a bad idea. I do want to avoid having too many questions. We could

Re: CEP-15 multi key transaction syntax

Monday Morning Caleb has digested, and here's where I am... 1.) I have no problem w/ having SELECT on the RHS of a LET assignment, and to be honest, this may make some implementation things easier for me (i.e. the encapsulation of SELECT within LET) 2.) I'm in favor of LET without a select,

Re: CEP-15 multi key transaction syntax

I am +1 on IS NOT NULL/IS NULL instead of EXISTS/NOT EXISTS Not requiring (but allowing) SELECT on LET Patrick On Mon, Aug 15, 2022 at 11:01 AM Caleb Rackliffe wrote: > Monday Morning Caleb has digested, and here's where I am... > > 1.) I have no problem w/ having SELECT on the RHS of a LET

Re: CEP-15 multi key transaction syntax

 > I like Benedict's tuple deconstruction idea For posterity, this was Avi’s idea! > On 15 Aug 2022, at 18:59, Caleb Rackliffe wrote: > > Monday Morning Caleb has digested, and here's where I am... > > 1.) I have no problem w/ having SELECT on the RHS of a LET assignment, and to > be

Re: [Proposal] add pull request template

> If there is consensus that the PR template is a good idea, I'll create a > branch and we can wrangle the words. > > I think the pull request generally is against a specific branch but having > the branch listed in the template is not a bad idea. I do want to avoid > having too many questions.

Re: CEP-15 multi key transaction syntax

Just updated the Jira to reflect the latest conversation here. On Mon, Aug 15, 2022 at 1:06 PM Patrick McFadin wrote: > I am +1 on > > IS NOT NULL/IS NULL instead of EXISTS/NOT EXISTS > > Not requiring (but allowing) SELECT on LET > >

Re: CEP-15 multi key transaction syntax

Ha, apologies to Avi ;) On Mon, Aug 15, 2022 at 2:01 PM Benedict Elliott Smith wrote: >  > > I like Benedict's tuple deconstruction idea > > > For posterity, this was Avi’s idea! > > On 15 Aug 2022, at 18:59, Caleb Rackliffe > wrote: > > Monday Morning Caleb has digested, and here's where I