[jira] [Created] (CALCITE-4176) Key descriptor can be optional in SESSION table function

Rui Wang created CALCITE-4176: - Summary: Key descriptor can be optional in SESSION table function Key: CALCITE-4176 URL: https://issues.apache.org/jira/browse/CALCITE-4176 Project: Calcite Issue

Re: [DISCUSS] Open SVN dist access to committers

Awesome! It really helps for the committers as release manager. Best, Chunwei On Fri, Aug 14, 2020 at 6:58 AM Julian Hyde wrote: > Thanks for the clarification, Sebb. We now know, and accept, that the risk > is non-zero. > > > On Aug 13, 2020, at 2:17 PM, sebbaz wrote: > > > > > > > > On

[jira] [Created] (CALCITE-4175) Add ability to create a connection and DSN from a Config

Josiah Goodson created CALCITE-4175: --- Summary: Add ability to create a connection and DSN from a Config Key: CALCITE-4175 URL: https://issues.apache.org/jira/browse/CALCITE-4175 Project: Calcite

Re: [DISCUSS] Release Managers

Thanks for volunteering, Ruben! I think you can be the release manager for 1.26.0. We still need 2 more volunteers for the next 2 versions. Thanks, Haisheng On 2020/07/25 15:24:43, Ruben Q L wrote: > Hi, > > I can volunteer for one of them, for example 1.26.0 > > Best regards, > Ruben > >

Re: [VOTE] Release apache-calcite-1.25.0 (release candidate 0)

Since the release vote has passed, Andrei as release manager can declare the master branch open for commits. Publishing the artifacts and making the release announcement can go on in parallel. > On Aug 13, 2020, at 3:37 PM, Andrei Sereda wrote: > > Hi Haisheng, > > Thanks for your reply. >

Re: [DISCUSS] Open SVN dist access to committers

Thanks for the clarification, Sebb. We now know, and accept, that the risk is non-zero. > On Aug 13, 2020, at 2:17 PM, sebbaz wrote: > > > > On 2020/08/13 18:47:54, Julian Hyde wrote: >> +1 >> >> Clearly committers should have read and write access to all non-private >> information in a

Re: [DISCUSS] Open SVN dist access to committers

+1 from me as well. From our side, the risk is minimized as the process to move the artifacts on SVN is automated using Vladimir's gradle plugin, so there shouldn't be any manual intervention on the part of the RM. Francis On 14/08/2020 8:34 am, Ruben Q L wrote: +1 Apart from the reasons

Re: [VOTE] Release apache-calcite-1.25.0 (release candidate 0)

Hi Haisheng, Thanks for your reply. There is a parallel discussion [1] about letting committers have write access to SVN dist repository. Seems like most people are on the same page (ie +1). If approved, I should be able to finalize the release soon myself. Andrei. [1]

Re: [DISCUSS] Open SVN dist access to committers

+1 Apart from the reasons already mentioned, if we want committers (not just PMC) to get involved in the release management process, I think this step would go in the right direction. Best regards, Ruben Le jeu. 13 août 2020 à 23:18, Rui Wang a écrit : > +1 > > if well used/tested svn

Re: [DISCUSS] Open SVN dist access to committers

+1 if well used/tested svn commands for releasing are documented, committers without experience on release or svn can still use those properly. -Rui On Thu, Aug 13, 2020 at 3:09 PM Stamatis Zampetakis wrote: > +1 > > I always thought that committers had access to the dist repo and I was >

Re: [DISCUSS] Open SVN dist access to committers

+1 I always thought that committers had access to the dist repo and I was completely fine with it. Everybody makes mistakes no matter if it is a committer or PMC so I don't see a reason to have different read/write access to the repo. Best, Stamatis On Fri, Aug 14, 2020 at 12:17 AM sebbaz

Re: [VOTE] Release apache-calcite-1.25.0 (release candidate 0)

Hi Andrei, Let's unblock the release as soon as possible. I can help publish the artifact. Can you cat build/stagingRepositories/nexus.txt and send me the content in your local repo? Thanks, Haisheng On 2020/08/13 14:47:05, Andrei Sereda wrote: > It can also be configured per project. > >

Re: [DISCUSS] Open SVN dist access to committers

On 2020/08/13 18:47:54, Julian Hyde wrote: > +1 > > Clearly committers should have read and write access to all non-private > information in a project. I don’t even think this needs a vote. If this > discussion quickly reaches consensus, as I assume it will, let’s just make it > so. > >

Re: [ANNOUNCE] Ruben Quesada Lopez joins Calcite PMC

Thanks for your hard work on the project and in the community, Ruben. Well deserved. Julian > On Aug 13, 2020, at 6:19 AM, Thomas Rebele wrote: > > Congrats, Ruben! > > Cordialement / Best Regards, > *Thomas Rebele* | R Developer | 18 rue du 4 septembre, 75002 Paris, France > |

Re: [DISCUSS] Open SVN dist access to committers

+1 Clearly committers should have read and write access to all non-private information in a project. I don’t even think this needs a vote. If this discussion quickly reaches consensus, as I assume it will, let’s just make it so. The hypothetical risk that a committer would (accidentally or

Re: [DISCUSSION] Rename master branch to main

Hi, +1 for me too. On Wed, Aug 12, 2020 at 11:07 AM Josh Elser wrote: > +1 change it. > > On 7/28/20 1:43 PM, Julian Hyde wrote: > > I am in favor of renaming ‘master’ to ‘main’. To most people it doesn’t > make any difference. To some, such as potential members currently outside > the

[DISCUSS] Open SVN dist access to committers

Hello, For the last two releases ([1] and [2]) committers were not able to finalize the release due to SVN restrictions. One of the PMC members had to step in order to distribute the artifacts. By default, only PMCs are allowed to make changes to dist

Re: [VOTE] Release apache-calcite-1.25.0 (release candidate 0)

It can also be configured per project. > Do you know if SVN access can be configured per project ? > Yes it can, if the PMC agrees to it, the dist area can be opened up to all project committers - a few PMCs have done this. On Thu, Aug 13, 2020 at 10:43 AM Andrei Sereda wrote: > Inquired with

Re: [VOTE] Release apache-calcite-1.25.0 (release candidate 0)

Inquired with INFRA-20681 seems like only PMCs can commit to dist SVN: > Are committers (which are not PMCs) allowed to commit to SVN dist repo ? > ..., nope, by default its PMC members only On Thu, Aug 13, 2020 at 9:27 AM Andrei Sereda

Re: [VOTE] Release apache-calcite-1.25.0 (release candidate 0)

Can someone from PMC pls publish the release ? Or maybe contact INFRA about svn permissions for committers vs PMCs ? I would like to avoid blocking calcite development for too long. On Wed, Aug 12, 2020 at 11:33 PM Chunwei Lei wrote: > > Once this release is done, we should consider whether

Re: [ANNOUNCE] Ruben Quesada Lopez joins Calcite PMC

Congrats, Ruben! Cordialement / Best Regards, *Thomas Rebele* | R Developer | 18 rue du 4 septembre, 75002 Paris, France | www.tibco.com On Thu, Aug 13, 2020 at 12:54 AM Francis Chuang wrote: > Congratulations, Ruben! > > Francis > > On 13/08/2020 3:43 am, Andrei Sereda wrote: > >

[jira] [Created] (CALCITE-4174) avatica-go should handle complex/long URLs

Josiah Goodson created CALCITE-4174: --- Summary: avatica-go should handle complex/long URLs Key: CALCITE-4174 URL: https://issues.apache.org/jira/browse/CALCITE-4174 Project: Calcite Issue

[jira] [Created] (CALCITE-4173) Add internal SEARCH operator and Sarg literal, replacing use of IN in RexCall

Julian Hyde created CALCITE-4173: Summary: Add internal SEARCH operator and Sarg literal, replacing use of IN in RexCall Key: CALCITE-4173 URL: https://issues.apache.org/jira/browse/CALCITE-4173