[jira] [Created] (CALCITE-4952) Enable use of RelMetadataQuery using a simplistic & slow proxy path

[Jacques Nadeau (Jira)]

Jacques Nadeau created CALCITE-4952:
---

 Summary: Enable use of RelMetadataQuery using a simplistic & slow 
proxy path
 Key: CALCITE-4952
 URL: https://issues.apache.org/jira/browse/CALCITE-4952
 Project: Calcite
  Issue Type: Improvement
  Components: core
Reporter: Jacques Nadeau
Assignee: Jacques Nadeau


As part of working on CALCITE-4882 and CALCITE-4928, it became clear that there 
should be a simple, non-janino implementation of RelMetadataQuery internals to 
help with debugging. I'm not sure when/how but as of right now the Reflective 
handlers can't be used with RelMetadataQuery without also using Janino.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Re: [ANNOUNCE] New committer: Alessandro Solimando

[Francis Chuang]

Congrats!

On 19/12/2021 8:48 am, Aman Sinha wrote:

Congrats Alessandro !  Well deserved.

On Sat, Dec 18, 2021 at 9:46 AM Zoltan Haindrich  wrote:


Congartulations Alessandro!

On 12/18/21 4:42 PM, Enrico Olivelli wrote:

Congrats!
Enrico

Il Sab 18 Dic 2021, 16:00 Alessandro Solimando <
alessandro.solima...@gmail.com> ha scritto:


Hello everyone,
it's an honour and privilege to be part of this great community, I have
really learned a lot over the years by following discussions and
contributing, I am looking forward to further collaborations.

My academic background touched upon query processing over

semi-structured

data (XML) and for the Semantic Web (Sparql, descriptions logics,
ontology-based data access, semantic query processing over DBMS).

After several years of work as a data engineer (big data processing and
machine learning), I have recently joined Cloudera's optimizer team,

where

I am working on Apache Hive (which extensively uses Apache Calcite).

Best regards,
Alessandro

On Sat, 18 Dec 2021 at 15:08, Stamatis Zampetakis 
wrote:


Apache Calcite's Project Management Committee (PMC) has invited

Alessandro

Solimando to become a committer, and we are pleased to announce that he

has

accepted.

Alessandro has been in the community for quite some time now with his

first

contribution dating back in 2018. Since then he pushed many fixes in

both

Calcite and Avatica touching parts of the core engine,
the Cassandra adapter, and materialized view matching. Apart from code
contributions, Alessandro provides valuable help to the community by

doing

reviews, answering questions in the devlist, and testing releases.

Alessandro, welcome, thank you for your contributions, and we look

forward

to your further interactions with the community! If you wish, please

feel

free to tell us more about yourself and what you are working on.

Stamatis (on behalf of the Apache Calcite PMC)

Re: [ANNOUNCE] New committer: Alessandro Solimando

[Aman Sinha]

Congrats Alessandro !  Well deserved.

On Sat, Dec 18, 2021 at 9:46 AM Zoltan Haindrich  wrote:

> Congartulations Alessandro!
>
> On 12/18/21 4:42 PM, Enrico Olivelli wrote:
> > Congrats!
> > Enrico
> >
> > Il Sab 18 Dic 2021, 16:00 Alessandro Solimando <
> > alessandro.solima...@gmail.com> ha scritto:
> >
> >> Hello everyone,
> >> it's an honour and privilege to be part of this great community, I have
> >> really learned a lot over the years by following discussions and
> >> contributing, I am looking forward to further collaborations.
> >>
> >> My academic background touched upon query processing over
> semi-structured
> >> data (XML) and for the Semantic Web (Sparql, descriptions logics,
> >> ontology-based data access, semantic query processing over DBMS).
> >>
> >> After several years of work as a data engineer (big data processing and
> >> machine learning), I have recently joined Cloudera's optimizer team,
> where
> >> I am working on Apache Hive (which extensively uses Apache Calcite).
> >>
> >> Best regards,
> >> Alessandro
> >>
> >> On Sat, 18 Dec 2021 at 15:08, Stamatis Zampetakis 
> >> wrote:
> >>
> >>> Apache Calcite's Project Management Committee (PMC) has invited
> >> Alessandro
> >>> Solimando to become a committer, and we are pleased to announce that he
> >> has
> >>> accepted.
> >>>
> >>> Alessandro has been in the community for quite some time now with his
> >> first
> >>> contribution dating back in 2018. Since then he pushed many fixes in
> both
> >>> Calcite and Avatica touching parts of the core engine,
> >>> the Cassandra adapter, and materialized view matching. Apart from code
> >>> contributions, Alessandro provides valuable help to the community by
> >> doing
> >>> reviews, answering questions in the devlist, and testing releases.
> >>>
> >>> Alessandro, welcome, thank you for your contributions, and we look
> >> forward
> >>> to your further interactions with the community! If you wish, please
> feel
> >>> free to tell us more about yourself and what you are working on.
> >>>
> >>> Stamatis (on behalf of the Apache Calcite PMC)
> >>>
> >>
> >
>

Re: Build failed in Jenkins: Calcite » Calcite-snapshots #13

[Vladimir Sitnikov]

There are issues, and it does fail quite often. It is really frustrating.

I can disable the test if you think it would be better.

Based on past experience, we almost never revisit disabled tests, and it
would look as if "server" passes tests, however, it corrupts data.

Vladimir

Re: [Calcite Release] Preparing for 1.29.0 Release

[Rui Wang]

Thanks for more information Julian. Then there should not have known
blockers at this moment.

Hi Alessandro,

I will wait for another 24 hours before blocking the main branch. It should
be enough time so please feel free to merge PR once there is no objection.

-Rui

On Sat, Dec 18, 2021 at 11:45 AM Alessandro Solimando <
alessandro.solima...@gmail.com> wrote:

> Hi everyone,
> I'd like to merge https://github.com/apache/calcite/pull/2628 (
> https://issues.apache.org/jira/browse/CALCITE-4917) which is ready if
> there
> are no objections.
>
> Since it's just adding an extra test it's not urgent at all, so if it
> causes any troubles it can be postponed after the release.
>
> Best regards,
> Alessandro
>
> On Sat, 18 Dec 2021 at 19:19, Julian Hyde  wrote:
>
> > Ah, I see Stamatis has Log4j covered:
> > https://issues.apache.org/jira/browse/CALCITE-4950 <
> > https://issues.apache.org/jira/browse/CALCITE-4950>.
> >
> > > On Dec 18, 2021, at 10:17 AM, Julian Hyde 
> > wrote:
> > >
> > > I think we should skip CALCITE-4907. There’s still discussion in its
> PR,
> > https://github.com/apache/calcite/pull/2620 <
> > https://github.com/apache/calcite/pull/2620>. I promise we’ll get it in
> > soon after the release.
> > >
> > > In other news, there’s a new Log4j version, 2.17, addressing a new
> > CVE[1]. Let’s get that in.
> > >
> > > Julian
> > >
> > > [1]
> >
> https://thehackernews.com/2021/12/apache-issues-3rd-patch-to-fix-new-high.html
> > <
> >
> https://thehackernews.com/2021/12/apache-issues-3rd-patch-to-fix-new-high.html
> > >
> > >
> > >> On Dec 18, 2021, at 6:58 AM, Vladimir Ozerov  > > wrote:
> > >>
> > >> Hi Xiong,
> > >>
> > >> Thank you very much.
> > >>
> > >> Vladimir.
> > >>
> > >> Сб, 18 дек. 2021 г. в 14:32, xiong duan  > nobigo...@gmail.com>>:
> > >>
> > >>> Hi Vladimir,
> > >>>
> > >>> I have merged.
> > >>>
> > >>> Vladimir Ozerov mailto:ppoze...@gmail.com>>
> > 于2021年12月18日周六 16:58写道：
> > >>>
> >  Hi Xiong,
> > 
> >  I've just resolved the conflicts.
> > 
> >  Regards,
> >  Vladimir.
> > 
> >  сб, 18 дек. 2021 г. в 10:48, xiong duan   > nobigo...@gmail.com>>:
> > 
> > > Hi, Vladimir.
> > >
> > > The PR[https://github.com/apache/calcite/pull/2464 <
> > https://github.com/apache/calcite/pull/2464>] looks good. If you
> > > have
> > > free time Please resolve the conflicts. Then we can merge it.
> > >
> > > Vladimir Ozerov mailto:ppoze...@gmail.com>>
> > 于2021年12月18日周六 15:20写道：
> > >
> > >> Hi,
> > >>
> > >> Could you please also merge
> > >> https://github.com/apache/calcite/pull/2464 <
> > https://github.com/apache/calcite/pull/2464> ? I guess it got stuck
> > >> somehow,
> > >> as all the comments are addressed. This issue forced us to create
> a
> >  copy
> > > of
> > >> the AggregateUnionTransposeRule in our project.
> > >>
> > >> Regards,
> > >> Vladimir
> > >>
> > >> Сб, 18 дек. 2021 г. в 09:51, Rui Wang  > >:
> > >>
> > >>> Thanks Julian!
> > >>>
> > >>> Now we will just decide whether to merge CALCITE-4907 or not,
> then
> > >>> I
> > > will
> > >>> lock the main branch and start the release process.
> > >>>
> > >>>
> > >>> -Rui
> > >>>
> > >>> On Fri, Dec 17, 2021 at 10:29 PM Julian Hyde <
> > >>> jhyde.apa...@gmail.com 
> > >
> > >>> wrote:
> > >>>
> >  Rui, I have merged CALCITE-4946.
> > 
> > > On Dec 17, 2021, at 10:21 PM, Rui Wang 
> > > wrote:
> > >
> > > Thanks Zhe.
> > >
> > > Hi Francesco,
> > >
> > > I left a comment in your PR. Can you take a look?
> > >
> > > -Rui
> > >
> > > On Fri, Dec 17, 2021 at 3:32 PM Zhe Hu 
> > >>> wrote:
> > >
> > >> Hi, Rui.
> > >> CALCITE-4860 will be fixed in next release, you can pass it
> > >> currently.
> > >> Thanks for your work!
> > >>
> > >>
> > >> Best,
> > >> ZheHu
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On 12/18/2021 06:08，Francesco Gini
> > > wrote：
> > >> https://issues.apache.org/jira/browse/CALCITE-4907 is in
> >  review.
> > > I
> >  believe
> > >> I have addressed all the comments. Let me know if I missed
> > > anything.
> > >>
> > >> On Fri, 17 Dec 2021 at 22:42, Jacques Nadeau <
> >  jacq...@apache.org>
> >  wrote:
> > >>
> > >> I've merged CALCITE-4948 to mitigate the concerns around
> > >> CALCITE-4898
> >  and
> > >> maven repositories and category x licenses.
> > >>
> > >> On Fri, Dec 17, 2021 at 1:02 PM Rui Wang <
> > >>> amaliu...@apache.org>
> > >>> wrote:
> > >>
> > >> For the 

Re: [Calcite Release] Preparing for 1.29.0 Release

[Alessandro Solimando]

Hi everyone,
I'd like to merge https://github.com/apache/calcite/pull/2628 (
https://issues.apache.org/jira/browse/CALCITE-4917) which is ready if there
are no objections.

Since it's just adding an extra test it's not urgent at all, so if it
causes any troubles it can be postponed after the release.

Best regards,
Alessandro

On Sat, 18 Dec 2021 at 19:19, Julian Hyde  wrote:

> Ah, I see Stamatis has Log4j covered:
> https://issues.apache.org/jira/browse/CALCITE-4950 <
> https://issues.apache.org/jira/browse/CALCITE-4950>.
>
> > On Dec 18, 2021, at 10:17 AM, Julian Hyde 
> wrote:
> >
> > I think we should skip CALCITE-4907. There’s still discussion in its PR,
> https://github.com/apache/calcite/pull/2620 <
> https://github.com/apache/calcite/pull/2620>. I promise we’ll get it in
> soon after the release.
> >
> > In other news, there’s a new Log4j version, 2.17, addressing a new
> CVE[1]. Let’s get that in.
> >
> > Julian
> >
> > [1]
> https://thehackernews.com/2021/12/apache-issues-3rd-patch-to-fix-new-high.html
> <
> https://thehackernews.com/2021/12/apache-issues-3rd-patch-to-fix-new-high.html
> >
> >
> >> On Dec 18, 2021, at 6:58 AM, Vladimir Ozerov  > wrote:
> >>
> >> Hi Xiong,
> >>
> >> Thank you very much.
> >>
> >> Vladimir.
> >>
> >> Сб, 18 дек. 2021 г. в 14:32, xiong duan  nobigo...@gmail.com>>:
> >>
> >>> Hi Vladimir,
> >>>
> >>> I have merged.
> >>>
> >>> Vladimir Ozerov mailto:ppoze...@gmail.com>>
> 于2021年12月18日周六 16:58写道：
> >>>
>  Hi Xiong,
> 
>  I've just resolved the conflicts.
> 
>  Regards,
>  Vladimir.
> 
>  сб, 18 дек. 2021 г. в 10:48, xiong duan  nobigo...@gmail.com>>:
> 
> > Hi, Vladimir.
> >
> > The PR[https://github.com/apache/calcite/pull/2464 <
> https://github.com/apache/calcite/pull/2464>] looks good. If you
> > have
> > free time Please resolve the conflicts. Then we can merge it.
> >
> > Vladimir Ozerov mailto:ppoze...@gmail.com>>
> 于2021年12月18日周六 15:20写道：
> >
> >> Hi,
> >>
> >> Could you please also merge
> >> https://github.com/apache/calcite/pull/2464 <
> https://github.com/apache/calcite/pull/2464> ? I guess it got stuck
> >> somehow,
> >> as all the comments are addressed. This issue forced us to create a
>  copy
> > of
> >> the AggregateUnionTransposeRule in our project.
> >>
> >> Regards,
> >> Vladimir
> >>
> >> Сб, 18 дек. 2021 г. в 09:51, Rui Wang  >:
> >>
> >>> Thanks Julian!
> >>>
> >>> Now we will just decide whether to merge CALCITE-4907 or not, then
> >>> I
> > will
> >>> lock the main branch and start the release process.
> >>>
> >>>
> >>> -Rui
> >>>
> >>> On Fri, Dec 17, 2021 at 10:29 PM Julian Hyde <
> >>> jhyde.apa...@gmail.com 
> >
> >>> wrote:
> >>>
>  Rui, I have merged CALCITE-4946.
> 
> > On Dec 17, 2021, at 10:21 PM, Rui Wang 
> > wrote:
> >
> > Thanks Zhe.
> >
> > Hi Francesco,
> >
> > I left a comment in your PR. Can you take a look?
> >
> > -Rui
> >
> > On Fri, Dec 17, 2021 at 3:32 PM Zhe Hu 
> >>> wrote:
> >
> >> Hi, Rui.
> >> CALCITE-4860 will be fixed in next release, you can pass it
> >> currently.
> >> Thanks for your work!
> >>
> >>
> >> Best,
> >> ZheHu
> >>
> >>
> >>
> >>
> >>
> >>
> >> On 12/18/2021 06:08，Francesco Gini
> > wrote：
> >> https://issues.apache.org/jira/browse/CALCITE-4907 is in
>  review.
> > I
>  believe
> >> I have addressed all the comments. Let me know if I missed
> > anything.
> >>
> >> On Fri, 17 Dec 2021 at 22:42, Jacques Nadeau <
>  jacq...@apache.org>
>  wrote:
> >>
> >> I've merged CALCITE-4948 to mitigate the concerns around
> >> CALCITE-4898
>  and
> >> maven repositories and category x licenses.
> >>
> >> On Fri, Dec 17, 2021 at 1:02 PM Rui Wang <
> >>> amaliu...@apache.org>
> >>> wrote:
> >>
> >> For the list of 1.29 fix Jira, several Jira have been marked
> >>> as
> >>> resolved
> >> since this Monday. I will do another pass today but probably
> >>> not
> > all
> >> those
> >> will make the 1.29.0 release.
> >>
> >>
> >> -Rui
> >>
> >> On Fri, Dec 17, 2021 at 11:57 AM Ruben Q L  
> >> wrote:
> >>
> >> Hello,
> >>
> >> FYI https://issues.apache.org/jira/browse/CALCITE-4737 has
> >>> been
> >> merged.
> >>
> >> Regards,
> >> Ruben
> >>
> >>
> >> On Fri, Dec 17, 2021 at 7:40 PM Julian Hyde <
> > jhyde.apa...@gmail.com
> 

Re: sqlnode design question

[Stamatis Zampetakis]

Hi,

Many people integrating Calcite with C++ or other languages opt to do so by
serializing/deserializing plans to JSON (see discussion [1] for example).

Before reimplementing part of Calcite in another language it may make sense
to look if you can achieve the desired result in a different way.

Best,
Stamatis

[1] https://lists.apache.org/thread/yd5lqls6pxfn7q1m0r2onbj3x4wvohln

On Wed, Dec 8, 2021 at 7:37 PM 许伟栋  wrote:

> Hi, All:
>
> I'm new to calcite, have some doubts about the SqlNode design:
>
> I'm working on a mysql middleware which needs parsing and query
> optimization.
> Unfortunately, I'm using C++, so it's not trivial to use Calcite directly.
>
> Instead, I'm trying to mimic what Calcite does to see if I can come up with
> an MVP.
>
> Right now, I got the CST from Antlr4, and I'm about to visit the CST to
> generate AST.
> When I look at SqlNode in Calcite, I found that a common segment like table
> from select statement is also the type of SqlNode.
> In other implementations, it's normally the concrete type like
> `TableSegment`.
> I was wondering what's the purpose behind the structure design?
>
> Thanks in advance.
>

Re: Build failed in Jenkins: Calcite » Calcite-snapshots #13

[Stamatis Zampetakis]

Thanks for looking into this Vladimir.

One bug does not justify dropping one module completely.

Moreover, end-users rarely follow the dev list so asking if somebody is
using may not be representative.

Personally, I find it useful and I think it is helping people build and
test DDL/DML parsers.

Best,
Stamatis

On Wed, Dec 15, 2021 at 12:13 PM Vladimir Sitnikov <
sitnikov.vladi...@gmail.com> wrote:

> The failure is known as https://issues.apache.org/jira/browse/CALCITE-4824
>
> Does anybody use calcite-server?
> Does anybody have cycles to maintain/fix calcite-server?
> Can we just remove it?
>
> Vladimir
>

Re: [DISCUSS] JIRA vs GitHub Issues

[Stamatis Zampetakis]

There are many good ideas in this thread and some of them we could probably
directly use without changing the current workflows a lot.

Inspired from the discussion so far my main suggestion would be to enable
and start using the GitHub milestones keeping a one-to-one mapping with
Calcite versions.

As other people have mentioned already, currently we allow JIRAless pull
requests and it does make sense in many cases (I will not repeat here what
others have said already). The drawback with the current process is that we
cannot associate a "fix version" if the PR does not have a JIRA and it
might be difficult to track down what changes went on which version. If we
have milestones then we can solve this inconvenience with some other added
benefits.

Note that I am not proposing to replace JIRA. People are free to create
JIRAs and/or pull requests. The difference is that every pull request
before it gets merged should have an assigned milestone. This small
addition in our workflow will make all patches (with or without JIRA)
easier to track.

The main goal of this change is to allow people to use JIRA, GitHub, or
both, as they prefer. This essentially means that we relax the requirement
to have a JIRA case for every patch. At a second time, we can introduce PR
templates to ensure all the necessary information is there when somebody
raises a PR.

If people think it's worth enabling GitHub milestones I can prepare a PR
with changes in the documentation to see concretely how this will
affect our current procedures. On the other hand, if nobody sees any
advantage in using milestones then I'm fine leaving things as they are
right now.

Best,
Stamatis

On Mon, Dec 6, 2021 at 7:33 PM Ruben Q L  wrote:

> Thanks for moving the discussion here, Vladimir.
>
> First of all, I honestly appreciate the fact that you launched this
> discussion, I think you raised some valid points; what you propose sounds
> reasonable, and it seems a valid approach too. My main argument is that I
> have no big issues with the current approach (which, of course, is not
> perfect).
>
> I guess my bottom-line is that I believe that issue tracking and version
> control (+ code review) are two different things, which serve two different
> purposes, and it is arguably a good thing to keep them separated: using
> Jira for the former and Github PRs for the latter is adequate IMO.
>
> > You did use GitHub for tracking already.
> As I see it, I have used Jira for issue tracking, and GitHub PRs for code
> review + merge. If you ask me, perhaps I am old-fashioned, but I think the
> development workflow should focus on the Jira ticket, and not on the GitHub
> PR.
>
> > Here's a good example: https://github.com/apache/calcite/pull/2329
> I agree it is a good example. The associated Jira has several comments with
> a high-level discussion, the PR contains code-review comments for technical
> details. I am happy with this decoupling, although sometimes this is not
> always the case in all tickets; perhaps we should clarify our current
> workflow and try to enforce some rules, instead of changing it into
> something completely new.
> It is also a good example because the Jira reporter and the PR creator were
> not the same person, plus there was a span of almost two years between the
> ticket creation and the PR submission. I know this is usually uncommon, but
> it shows that there are two different roles / actions: one thing is
> describing / analyzing an issue; and a second, different thing is carrying
> out its implementation (with its corresponding code review).
>
> > GitHub allows links, and links have no properties like "caused by",
> "duplicated by". However, basic links are just enough for Calcite.
> I think it would be sad to lose this feature, but I admit it is a minor
> detail.
>
> > If you have a "customized dashboard" that is useful for many
> contributors, please show it.
> I was thinking for example at the dashboard mentioned by Stamatis, which is
> very useful (not only for the release manager, but for all contributors)
> when a release date is coming.
>
> Best regards,
> Ruben
>
>
> On Mon, Dec 6, 2021 at 12:44 PM Vladimir Sitnikov <
> sitnikov.vladi...@gmail.com> wrote:
>
> > Moving the reply to DISCUSS thread.
> >
> > Ruben>My vote might be biased because I have used Jira for many years
> (and
> > I have
> > Ruben>never used Github for issue tracking).
> >
> > It is really sad to hear.
> > You authored 87 PRs for Calcite!
> > You did use GitHub for tracking already.
> >
> >
> https://github.com/apache/calcite/pulls?q=is%3Apr+author%3Arubenada+is%3Aclosed
> >
> > Here's a good example: https://github.com/apache/calcite/pull/2329
> > PR description says the intention of the feature.
> > There are overall and line-targeted comments.
> > Creating GitHub Issue is not that different from creating a PR.
> >
> > Ruben>I have the impression that some of the problems described
> discussion
> > are
> > Ruben>not per se Jira-related, but they appear 

Re: [Calcite Release] Preparing for 1.29.0 Release

[Julian Hyde]

Ah, I see Stamatis has Log4j covered: 
https://issues.apache.org/jira/browse/CALCITE-4950 
. 

> On Dec 18, 2021, at 10:17 AM, Julian Hyde  wrote:
> 
> I think we should skip CALCITE-4907. There’s still discussion in its PR, 
> https://github.com/apache/calcite/pull/2620 
> . I promise we’ll get it in soon 
> after the release.
> 
> In other news, there’s a new Log4j version, 2.17, addressing a new CVE[1]. 
> Let’s get that in.
> 
> Julian
> 
> [1] 
> https://thehackernews.com/2021/12/apache-issues-3rd-patch-to-fix-new-high.html
>  
> 
> 
>> On Dec 18, 2021, at 6:58 AM, Vladimir Ozerov > > wrote:
>> 
>> Hi Xiong,
>> 
>> Thank you very much.
>> 
>> Vladimir.
>> 
>> Сб, 18 дек. 2021 г. в 14:32, xiong duan > >:
>> 
>>> Hi Vladimir,
>>> 
>>> I have merged.
>>> 
>>> Vladimir Ozerov mailto:ppoze...@gmail.com>> 
>>> 于2021年12月18日周六 16:58写道：
>>> 
 Hi Xiong,
 
 I've just resolved the conflicts.
 
 Regards,
 Vladimir.
 
 сб, 18 дек. 2021 г. в 10:48, xiong duan >>> >:
 
> Hi, Vladimir.
> 
> The PR[https://github.com/apache/calcite/pull/2464 
> ] looks good. If you
> have
> free time Please resolve the conflicts. Then we can merge it.
> 
> Vladimir Ozerov mailto:ppoze...@gmail.com>> 
> 于2021年12月18日周六 15:20写道：
> 
>> Hi,
>> 
>> Could you please also merge
>> https://github.com/apache/calcite/pull/2464 
>>  ? I guess it got stuck
>> somehow,
>> as all the comments are addressed. This issue forced us to create a
 copy
> of
>> the AggregateUnionTransposeRule in our project.
>> 
>> Regards,
>> Vladimir
>> 
>> Сб, 18 дек. 2021 г. в 09:51, Rui Wang > >:
>> 
>>> Thanks Julian!
>>> 
>>> Now we will just decide whether to merge CALCITE-4907 or not, then
>>> I
> will
>>> lock the main branch and start the release process.
>>> 
>>> 
>>> -Rui
>>> 
>>> On Fri, Dec 17, 2021 at 10:29 PM Julian Hyde <
>>> jhyde.apa...@gmail.com 
> 
>>> wrote:
>>> 
 Rui, I have merged CALCITE-4946.
 
> On Dec 17, 2021, at 10:21 PM, Rui Wang 
> wrote:
> 
> Thanks Zhe.
> 
> Hi Francesco,
> 
> I left a comment in your PR. Can you take a look?
> 
> -Rui
> 
> On Fri, Dec 17, 2021 at 3:32 PM Zhe Hu 
>>> wrote:
> 
>> Hi, Rui.
>> CALCITE-4860 will be fixed in next release, you can pass it
>> currently.
>> Thanks for your work!
>> 
>> 
>> Best,
>> ZheHu
>> 
>> 
>> 
>> 
>> 
>> 
>> On 12/18/2021 06:08，Francesco Gini
> wrote：
>> https://issues.apache.org/jira/browse/CALCITE-4907 is in
 review.
> I
 believe
>> I have addressed all the comments. Let me know if I missed
> anything.
>> 
>> On Fri, 17 Dec 2021 at 22:42, Jacques Nadeau <
 jacq...@apache.org>
 wrote:
>> 
>> I've merged CALCITE-4948 to mitigate the concerns around
>> CALCITE-4898
 and
>> maven repositories and category x licenses.
>> 
>> On Fri, Dec 17, 2021 at 1:02 PM Rui Wang <
>>> amaliu...@apache.org>
>>> wrote:
>> 
>> For the list of 1.29 fix Jira, several Jira have been marked
>>> as
>>> resolved
>> since this Monday. I will do another pass today but probably
>>> not
> all
>> those
>> will make the 1.29.0 release.
>> 
>> 
>> -Rui
>> 
>> On Fri, Dec 17, 2021 at 11:57 AM Ruben Q L >>> 
>> wrote:
>> 
>> Hello,
>> 
>> FYI https://issues.apache.org/jira/browse/CALCITE-4737 has
>>> been
>> merged.
>> 
>> Regards,
>> Ruben
>> 
>> 
>> On Fri, Dec 17, 2021 at 7:40 PM Julian Hyde <
> jhyde.apa...@gmail.com
>>> 
>> wrote:
>> 
>> Rui,
>> 
>> Even though
>>> https://issues.apache.org/jira/browse/CALCITE-4898
 <
>> https://issues.apache.org/jira/browse/CALCITE-4898> is marked
>> fixed,
>> there’s some fallout regarding maven repositories and category
 X.
>> That
>> needs to be sorted out before RC0. See [1].
>> 
>> I’m working on getting
>> https://issues.apache.org/jira/browse/CALCITE-4946
>>  done
 today.
>> 

Re: [Calcite Release] Preparing for 1.29.0 Release

[Julian Hyde]

I think we should skip CALCITE-4907. There’s still discussion in its PR, 
https://github.com/apache/calcite/pull/2620 
. I promise we’ll get it in soon 
after the release.

In other news, there’s a new Log4j version, 2.17, addressing a new CVE[1]. 
Let’s get that in.

Julian

[1] 
https://thehackernews.com/2021/12/apache-issues-3rd-patch-to-fix-new-high.html

> On Dec 18, 2021, at 6:58 AM, Vladimir Ozerov  wrote:
> 
> Hi Xiong,
> 
> Thank you very much.
> 
> Vladimir.
> 
> Сб, 18 дек. 2021 г. в 14:32, xiong duan :
> 
>> Hi Vladimir,
>> 
>> I have merged.
>> 
>> Vladimir Ozerov  于2021年12月18日周六 16:58写道：
>> 
>>> Hi Xiong,
>>> 
>>> I've just resolved the conflicts.
>>> 
>>> Regards,
>>> Vladimir.
>>> 
>>> сб, 18 дек. 2021 г. в 10:48, xiong duan :
>>> 
 Hi, Vladimir.
 
 The PR[https://github.com/apache/calcite/pull/2464] looks good. If you
 have
 free time Please resolve the conflicts. Then we can merge it.
 
 Vladimir Ozerov  于2021年12月18日周六 15:20写道：
 
> Hi,
> 
> Could you please also merge
> https://github.com/apache/calcite/pull/2464 ? I guess it got stuck
> somehow,
> as all the comments are addressed. This issue forced us to create a
>>> copy
 of
> the AggregateUnionTransposeRule in our project.
> 
> Regards,
> Vladimir
> 
> Сб, 18 дек. 2021 г. в 09:51, Rui Wang :
> 
>> Thanks Julian!
>> 
>> Now we will just decide whether to merge CALCITE-4907 or not, then
>> I
 will
>> lock the main branch and start the release process.
>> 
>> 
>> -Rui
>> 
>> On Fri, Dec 17, 2021 at 10:29 PM Julian Hyde <
>> jhyde.apa...@gmail.com
 
>> wrote:
>> 
>>> Rui, I have merged CALCITE-4946.
>>> 
 On Dec 17, 2021, at 10:21 PM, Rui Wang 
 wrote:
 
 Thanks Zhe.
 
 Hi Francesco,
 
 I left a comment in your PR. Can you take a look?
 
 -Rui
 
 On Fri, Dec 17, 2021 at 3:32 PM Zhe Hu 
>> wrote:
 
> Hi, Rui.
> CALCITE-4860 will be fixed in next release, you can pass it
> currently.
> Thanks for your work!
> 
> 
> Best,
> ZheHu
> 
> 
> 
> 
> 
> 
> On 12/18/2021 06:08，Francesco Gini
 wrote：
> https://issues.apache.org/jira/browse/CALCITE-4907 is in
>>> review.
 I
>>> believe
> I have addressed all the comments. Let me know if I missed
 anything.
> 
> On Fri, 17 Dec 2021 at 22:42, Jacques Nadeau <
>>> jacq...@apache.org>
>>> wrote:
> 
> I've merged CALCITE-4948 to mitigate the concerns around
> CALCITE-4898
>>> and
> maven repositories and category x licenses.
> 
> On Fri, Dec 17, 2021 at 1:02 PM Rui Wang <
>> amaliu...@apache.org>
>> wrote:
> 
> For the list of 1.29 fix Jira, several Jira have been marked
>> as
>> resolved
> since this Monday. I will do another pass today but probably
>> not
 all
> those
> will make the 1.29.0 release.
> 
> 
> -Rui
> 
> On Fri, Dec 17, 2021 at 11:57 AM Ruben Q L >> 
> wrote:
> 
> Hello,
> 
> FYI https://issues.apache.org/jira/browse/CALCITE-4737 has
>> been
> merged.
> 
> Regards,
> Ruben
> 
> 
> On Fri, Dec 17, 2021 at 7:40 PM Julian Hyde <
 jhyde.apa...@gmail.com
>> 
> wrote:
> 
> Rui,
> 
> Even though
>> https://issues.apache.org/jira/browse/CALCITE-4898
>>> <
> https://issues.apache.org/jira/browse/CALCITE-4898> is marked
> fixed,
> there’s some fallout regarding maven repositories and category
>>> X.
> That
> needs to be sorted out before RC0. See [1].
> 
> I’m working on getting
> https://issues.apache.org/jira/browse/CALCITE-4946
>  done
>>> today.
> Please
> wait for that.
> 
> https://issues.apache.org/jira/browse/CALCITE-4885 <
> https://issues.apache.org/jira/browse/CALCITE-4885> is a big
> refactoring
> and, though I’d love to get it in before the release, it isn’t
 going
> to
> happen. Don’t wait for it.
> 
> I also see the following as open or in progress and
>> fix-in-1.29:
> * https://issues.apache.org/jira/browse/CALCITE-4872 <
> https://issues.apache.org/jira/browse/CALCITE-4872> (Will
>>> Noble)
> * https://issues.apache.org/jira/browse/CALCITE-4908 <
> https://issues.apache.org/jira/browse/CALCITE-4908> (Woonsan
>>> Koo)
> * https://issues.apache.org/jira/browse/CALCITE-4704 <
> 

Re: [ANNOUNCE] New committer: Alessandro Solimando

[Zoltan Haindrich]

Congartulations Alessandro!

On 12/18/21 4:42 PM, Enrico Olivelli wrote:

Congrats!
Enrico

Il Sab 18 Dic 2021, 16:00 Alessandro Solimando <
alessandro.solima...@gmail.com> ha scritto:


Hello everyone,
it's an honour and privilege to be part of this great community, I have
really learned a lot over the years by following discussions and
contributing, I am looking forward to further collaborations.

My academic background touched upon query processing over semi-structured
data (XML) and for the Semantic Web (Sparql, descriptions logics,
ontology-based data access, semantic query processing over DBMS).

After several years of work as a data engineer (big data processing and
machine learning), I have recently joined Cloudera's optimizer team, where
I am working on Apache Hive (which extensively uses Apache Calcite).

Best regards,
Alessandro

On Sat, 18 Dec 2021 at 15:08, Stamatis Zampetakis 
wrote:


Apache Calcite's Project Management Committee (PMC) has invited

Alessandro

Solimando to become a committer, and we are pleased to announce that he

has

accepted.

Alessandro has been in the community for quite some time now with his

first

contribution dating back in 2018. Since then he pushed many fixes in both
Calcite and Avatica touching parts of the core engine,
the Cassandra adapter, and materialized view matching. Apart from code
contributions, Alessandro provides valuable help to the community by

doing

reviews, answering questions in the devlist, and testing releases.

Alessandro, welcome, thank you for your contributions, and we look

forward

to your further interactions with the community! If you wish, please feel
free to tell us more about yourself and what you are working on.

Stamatis (on behalf of the Apache Calcite PMC)

Jenkins build is back to normal : Calcite » Calcite-snapshots #23

[Apache Jenkins Server]

See 

Re: [ANNOUNCE] New committer: Alessandro Solimando

[Enrico Olivelli]

Congrats!
Enrico

Il Sab 18 Dic 2021, 16:00 Alessandro Solimando <
alessandro.solima...@gmail.com> ha scritto:

> Hello everyone,
> it's an honour and privilege to be part of this great community, I have
> really learned a lot over the years by following discussions and
> contributing, I am looking forward to further collaborations.
>
> My academic background touched upon query processing over semi-structured
> data (XML) and for the Semantic Web (Sparql, descriptions logics,
> ontology-based data access, semantic query processing over DBMS).
>
> After several years of work as a data engineer (big data processing and
> machine learning), I have recently joined Cloudera's optimizer team, where
> I am working on Apache Hive (which extensively uses Apache Calcite).
>
> Best regards,
> Alessandro
>
> On Sat, 18 Dec 2021 at 15:08, Stamatis Zampetakis 
> wrote:
>
> > Apache Calcite's Project Management Committee (PMC) has invited
> Alessandro
> > Solimando to become a committer, and we are pleased to announce that he
> has
> > accepted.
> >
> > Alessandro has been in the community for quite some time now with his
> first
> > contribution dating back in 2018. Since then he pushed many fixes in both
> > Calcite and Avatica touching parts of the core engine,
> > the Cassandra adapter, and materialized view matching. Apart from code
> > contributions, Alessandro provides valuable help to the community by
> doing
> > reviews, answering questions in the devlist, and testing releases.
> >
> > Alessandro, welcome, thank you for your contributions, and we look
> forward
> > to your further interactions with the community! If you wish, please feel
> > free to tell us more about yourself and what you are working on.
> >
> > Stamatis (on behalf of the Apache Calcite PMC)
> >
>

Re: [ANNOUNCE] New committer: Alessandro Solimando

[Alessandro Solimando]

Hello everyone,
it's an honour and privilege to be part of this great community, I have
really learned a lot over the years by following discussions and
contributing, I am looking forward to further collaborations.

My academic background touched upon query processing over semi-structured
data (XML) and for the Semantic Web (Sparql, descriptions logics,
ontology-based data access, semantic query processing over DBMS).

After several years of work as a data engineer (big data processing and
machine learning), I have recently joined Cloudera's optimizer team, where
I am working on Apache Hive (which extensively uses Apache Calcite).

Best regards,
Alessandro

On Sat, 18 Dec 2021 at 15:08, Stamatis Zampetakis  wrote:

> Apache Calcite's Project Management Committee (PMC) has invited Alessandro
> Solimando to become a committer, and we are pleased to announce that he has
> accepted.
>
> Alessandro has been in the community for quite some time now with his first
> contribution dating back in 2018. Since then he pushed many fixes in both
> Calcite and Avatica touching parts of the core engine,
> the Cassandra adapter, and materialized view matching. Apart from code
> contributions, Alessandro provides valuable help to the community by doing
> reviews, answering questions in the devlist, and testing releases.
>
> Alessandro, welcome, thank you for your contributions, and we look forward
> to your further interactions with the community! If you wish, please feel
> free to tell us more about yourself and what you are working on.
>
> Stamatis (on behalf of the Apache Calcite PMC)
>

Re: [Calcite Release] Preparing for 1.29.0 Release

[Vladimir Ozerov]

Hi Xiong,

Thank you very much.

Vladimir.

Сб, 18 дек. 2021 г. в 14:32, xiong duan :

> Hi Vladimir,
>
> I have merged.
>
> Vladimir Ozerov  于2021年12月18日周六 16:58写道：
>
> > Hi Xiong,
> >
> > I've just resolved the conflicts.
> >
> > Regards,
> > Vladimir.
> >
> > сб, 18 дек. 2021 г. в 10:48, xiong duan :
> >
> > > Hi, Vladimir.
> > >
> > > The PR[https://github.com/apache/calcite/pull/2464] looks good. If you
> > > have
> > > free time Please resolve the conflicts. Then we can merge it.
> > >
> > > Vladimir Ozerov  于2021年12月18日周六 15:20写道：
> > >
> > > > Hi,
> > > >
> > > > Could you please also merge
> > > > https://github.com/apache/calcite/pull/2464 ? I guess it got stuck
> > > > somehow,
> > > > as all the comments are addressed. This issue forced us to create a
> > copy
> > > of
> > > > the AggregateUnionTransposeRule in our project.
> > > >
> > > > Regards,
> > > > Vladimir
> > > >
> > > > Сб, 18 дек. 2021 г. в 09:51, Rui Wang :
> > > >
> > > > > Thanks Julian!
> > > > >
> > > > > Now we will just decide whether to merge CALCITE-4907 or not, then
> I
> > > will
> > > > > lock the main branch and start the release process.
> > > > >
> > > > >
> > > > > -Rui
> > > > >
> > > > > On Fri, Dec 17, 2021 at 10:29 PM Julian Hyde <
> jhyde.apa...@gmail.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Rui, I have merged CALCITE-4946.
> > > > > >
> > > > > > > On Dec 17, 2021, at 10:21 PM, Rui Wang 
> > > wrote:
> > > > > > >
> > > > > > > Thanks Zhe.
> > > > > > >
> > > > > > > Hi Francesco,
> > > > > > >
> > > > > > > I left a comment in your PR. Can you take a look?
> > > > > > >
> > > > > > > -Rui
> > > > > > >
> > > > > > > On Fri, Dec 17, 2021 at 3:32 PM Zhe Hu 
> wrote:
> > > > > > >
> > > > > > >> Hi, Rui.
> > > > > > >> CALCITE-4860 will be fixed in next release, you can pass it
> > > > currently.
> > > > > > >> Thanks for your work!
> > > > > > >>
> > > > > > >>
> > > > > > >> Best,
> > > > > > >> ZheHu
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >> On 12/18/2021 06:08，Francesco Gini
> > > wrote：
> > > > > > >> https://issues.apache.org/jira/browse/CALCITE-4907 is in
> > review.
> > > I
> > > > > > believe
> > > > > > >> I have addressed all the comments. Let me know if I missed
> > > anything.
> > > > > > >>
> > > > > > >> On Fri, 17 Dec 2021 at 22:42, Jacques Nadeau <
> > jacq...@apache.org>
> > > > > > wrote:
> > > > > > >>
> > > > > > >> I've merged CALCITE-4948 to mitigate the concerns around
> > > > CALCITE-4898
> > > > > > and
> > > > > > >> maven repositories and category x licenses.
> > > > > > >>
> > > > > > >> On Fri, Dec 17, 2021 at 1:02 PM Rui Wang <
> amaliu...@apache.org>
> > > > > wrote:
> > > > > > >>
> > > > > > >> For the list of 1.29 fix Jira, several Jira have been marked
> as
> > > > > resolved
> > > > > > >> since this Monday. I will do another pass today but probably
> not
> > > all
> > > > > > >> those
> > > > > > >> will make the 1.29.0 release.
> > > > > > >>
> > > > > > >>
> > > > > > >> -Rui
> > > > > > >>
> > > > > > >> On Fri, Dec 17, 2021 at 11:57 AM Ruben Q L  >
> > > > wrote:
> > > > > > >>
> > > > > > >> Hello,
> > > > > > >>
> > > > > > >> FYI https://issues.apache.org/jira/browse/CALCITE-4737 has
> been
> > > > > > >> merged.
> > > > > > >>
> > > > > > >> Regards,
> > > > > > >> Ruben
> > > > > > >>
> > > > > > >>
> > > > > > >> On Fri, Dec 17, 2021 at 7:40 PM Julian Hyde <
> > > jhyde.apa...@gmail.com
> > > > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> Rui,
> > > > > > >>
> > > > > > >> Even though
> https://issues.apache.org/jira/browse/CALCITE-4898
> > <
> > > > > > >> https://issues.apache.org/jira/browse/CALCITE-4898> is marked
> > > > fixed,
> > > > > > >> there’s some fallout regarding maven repositories and category
> > X.
> > > > > > >> That
> > > > > > >> needs to be sorted out before RC0. See [1].
> > > > > > >>
> > > > > > >> I’m working on getting
> > > > > > >> https://issues.apache.org/jira/browse/CALCITE-4946
> > > > > > >>  done
> > today.
> > > > > > >> Please
> > > > > > >> wait for that.
> > > > > > >>
> > > > > > >> https://issues.apache.org/jira/browse/CALCITE-4885 <
> > > > > > >> https://issues.apache.org/jira/browse/CALCITE-4885> is a big
> > > > > > >> refactoring
> > > > > > >> and, though I’d love to get it in before the release, it isn’t
> > > going
> > > > > > >> to
> > > > > > >> happen. Don’t wait for it.
> > > > > > >>
> > > > > > >> I also see the following as open or in progress and
> fix-in-1.29:
> > > > > > >> * https://issues.apache.org/jira/browse/CALCITE-4872 <
> > > > > > >> https://issues.apache.org/jira/browse/CALCITE-4872> (Will
> > Noble)
> > > > > > >> * https://issues.apache.org/jira/browse/CALCITE-4908 <
> > > > > > >> https://issues.apache.org/jira/browse/CALCITE-4908> (Woonsan
> > Koo)
> > > > > > >> * https://issues.apache.org/jira/browse/CALCITE-4704 <
> > > > > > >> 

Re: [ANNOUNCE] New committer: Alessandro Solimando

[xiong duan]

Congratulations Alessandro!

Michael Mior  于2021年12月18日周六 22:46写道：

> Congratulations Alessandro!
> --
> Michael Mior
> mm...@apache.org
>
> Le sam. 18 déc. 2021 à 09:09, Stamatis Zampetakis  a
> écrit :
> >
> > Apache Calcite's Project Management Committee (PMC) has invited
> Alessandro
> > Solimando to become a committer, and we are pleased to announce that he
> has
> > accepted.
> >
> > Alessandro has been in the community for quite some time now with his
> first
> > contribution dating back in 2018. Since then he pushed many fixes in both
> > Calcite and Avatica touching parts of the core engine,
> > the Cassandra adapter, and materialized view matching. Apart from code
> > contributions, Alessandro provides valuable help to the community by
> doing
> > reviews, answering questions in the devlist, and testing releases.
> >
> > Alessandro, welcome, thank you for your contributions, and we look
> forward
> > to your further interactions with the community! If you wish, please feel
> > free to tell us more about yourself and what you are working on.
> >
> > Stamatis (on behalf of the Apache Calcite PMC)
>

Re: [ANNOUNCE] New committer: Alessandro Solimando

[Michael Mior]

Congratulations Alessandro!
--
Michael Mior
mm...@apache.org

Le sam. 18 déc. 2021 à 09:09, Stamatis Zampetakis  a écrit :
>
> Apache Calcite's Project Management Committee (PMC) has invited Alessandro
> Solimando to become a committer, and we are pleased to announce that he has
> accepted.
>
> Alessandro has been in the community for quite some time now with his first
> contribution dating back in 2018. Since then he pushed many fixes in both
> Calcite and Avatica touching parts of the core engine,
> the Cassandra adapter, and materialized view matching. Apart from code
> contributions, Alessandro provides valuable help to the community by doing
> reviews, answering questions in the devlist, and testing releases.
>
> Alessandro, welcome, thank you for your contributions, and we look forward
> to your further interactions with the community! If you wish, please feel
> free to tell us more about yourself and what you are working on.
>
> Stamatis (on behalf of the Apache Calcite PMC)

Re:[ANNOUNCE] New committer: Alessandro Solimando

[Zhe Hu]

Congratulations! Alessandro Solimando.


On 12/18/2021 22:08，Stamatis Zampetakis wrote：
Apache Calcite's Project Management Committee (PMC) has invited Alessandro
Solimando to become a committer, and we are pleased to announce that he has
accepted.

Alessandro has been in the community for quite some time now with his first
contribution dating back in 2018. Since then he pushed many fixes in both
Calcite and Avatica touching parts of the core engine,
the Cassandra adapter, and materialized view matching. Apart from code
contributions, Alessandro provides valuable help to the community by doing
reviews, answering questions in the devlist, and testing releases.

Alessandro, welcome, thank you for your contributions, and we look forward
to your further interactions with the community! If you wish, please feel
free to tell us more about yourself and what you are working on.

Stamatis (on behalf of the Apache Calcite PMC)

[ANNOUNCE] New committer: Alessandro Solimando

[Stamatis Zampetakis]

Apache Calcite's Project Management Committee (PMC) has invited Alessandro
Solimando to become a committer, and we are pleased to announce that he has
accepted.

Alessandro has been in the community for quite some time now with his first
contribution dating back in 2018. Since then he pushed many fixes in both
Calcite and Avatica touching parts of the core engine,
the Cassandra adapter, and materialized view matching. Apart from code
contributions, Alessandro provides valuable help to the community by doing
reviews, answering questions in the devlist, and testing releases.

Alessandro, welcome, thank you for your contributions, and we look forward
to your further interactions with the community! If you wish, please feel
free to tell us more about yourself and what you are working on.

Stamatis (on behalf of the Apache Calcite PMC)

Re: Re: [DISCUSS] Apache Calcite Online Meetup January 2022

[Stamatis Zampetakis]

Thanks for the feedback Ioan, it's good to know what people think so that
we can improve the content.

I don't know if you checked them already but there are quite a few
interesting talks about Calcite listed in the website [1].
Among them there is also another version of the "tutorial" [2] with a bit
more time spent on introductory concepts like relational algebra etc.

To those who are still planning to present something in the meetup: It
would be good if you can share title, abstract, and duration so that I can
create the meetup event.

Best,
Stamatis

[1] https://calcite.apache.org/community/#talks
[2] https://youtu.be/p1O3E33FIs8

On Thu, Dec 16, 2021 at 1:20 AM Ioan Eugen Stan  wrote:

> Hi,
>
> Great idea with the meetup.
>
> I've watched that talk and gone through the tutorial code - submitted some
> feedback and here is some more:
>
> It's been VERY useful and I appreciate the work you do for Calcite and
> documentation.
> Regarding the training (youtube video) also hard to follow for a
> calcite/relational algebra beginner like me.
> I think an even gentler introduction / quick start is needed (not
> necessarily during meetup, but for newcomers in general).
>
> I found the online video to go quite fast into explaining Calcite classes
> and WHAT needs to be implemented but it was hard for me to understand WHY -
> or I need more intermediate steps.
> I had to go through the talk, the code and other code examples to better
> understand things.
>
> So these online resources (videos, talks, blogs, tutorials and code
> samples) are VERY welcomed.
>
> Although I am new to Calcite I might submit a small 5 min lightning talk
> if I have time to validate my idea :) .
>
> On 2021/11/23 18:34:59 Julian Hyde wrote:
> > +1 for Jan 19
> >
> > It would be great if Stamatis repeated one or two of the segments of
> > his tutorial at BOSS. (I was co-presenter but you've all heard enough
> > from me.) The material about adapters is foundational to understanding
> > Calcite. It could happen on Jan 19 or at another meetup in a couple of
> > months.
> >
> > Julian
> >
> >
> > On Tue, Nov 23, 2021 at 1:55 AM Stamatis Zampetakis 
> wrote:
> > >
> > > Thanks everyone for the feedback!
> > >
> > > @ Vladimir O, Vladimir S: Thanks for proposing to give a talk.
> > > I believe both topics will be very interesting for the community.
> > > When you settle up on what you would like to present please share an
> > > abstract & duration for the talk.
> > >
> > > Since there is interest and we already have 1-2 people willing to give
> a
> > > talk, I would suggest fixing the date/time as soon as possible.
> > > How about Wednesday, 19 January 2022, 17:00 UTC [1] ?
> > >
> > > If more people express interest in giving a talk we can either fit it
> to
> > > the same meetup or organise another meetup in 2-3 months after.
> > >
> > > Best,
> > > Stamatis
> > >
> > > [1]
> https://www.timeanddate.com/worldclock/fixedtime.html?iso=20220119T1700
> > >
> > > On Tue, Nov 23, 2021 at 12:05 AM Haisheng Yuan
> > >  wrote:
> > >
> > > > +1 for online meetup.
> > > >
> > > > - Haisheng
> > > >
> > > > --
> > > > Sender:Julian Hyde
> > > > Date:2021/11/23 00:58:25
> > > > Recipient:
> > > > Theme:Re: [DISCUSS] Apache Calcite Online Meetup January 2022
> > > >
> > > > +1
> > > >
> > > > Thanks for suggesting this, Stamatis.
> > > >
> > > > Julian
> > > >
> > > > > On Nov 22, 2021, at 7:12 AM, Zhe Hu  wrote:
> > > > >
> > > > > Got it. Thanks！
> > > > > |
> > > > >
> > > > >
> > > > > |
> > > > >  Replied Message 
> > > > > | From | xiong duan |
> > > > > | Date | 11/22/2021 23:09 |
> > > > > | To | dev |
> > > > > | Subject | Re: [DISCUSS] Apache Calcite Online Meetup January
> 2022 |
> > > > > Yes. You can find the relative talks in
> > > > > http://calcite.apache.org/community/#talks .
> > > > >
> > > > > Zhe Hu  于2021年11月22日周一 下午10:50写道：
> > > > >
> > > > >> +1 for online meetup.
> > > > >> And I’m curious about if there is any playback for this meetup,
> because
> > > > >> somebody might couldn't attend due to timezone variety or any
> other
> > > > reasons.
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> On 11/22/2021 22:26，xiong duan wrote：
> > > > >> Great idea. +1 for an online meetup.
> > > > >>
> > > > >> Justin Swanhart  于2021年11月20日周六 上午12:42写道：
> > > > >>
> > > > >> +1 for an online meetup
> > > > >>
> > > > >> On Fri, Nov 19, 2021, 11:32 AM Jacques Nadeau  >
> > > > wrote:
> > > > >>
> > > > >> WRT to talk structure, I propose we do 5 or 10 minute lightning
> talks as
> > > > >> opposed to something longer. It ensures a wider variety of topics,
> > > > better
> > > > >> attendance and you never have to sit that long through something
> you're
> > > > >> not
> > > > >> interested in...
> > > > >>
> > > > >> On Thu, Nov 18, 2021 at 11:47 PM Vladimir Sitnikov <
> > > > >> sitnikov.vladi...@gmail.com> wrote:
> > > > >>
> > > > >> Are 

[jira] [Created] (CALCITE-4951) Upgrade log4j2 version to 2.17.0 in Avatica

[Stamatis Zampetakis (Jira)]

Stamatis Zampetakis created CALCITE-4951:


 Summary: Upgrade log4j2 version to 2.17.0 in Avatica
 Key: CALCITE-4951
 URL: https://issues.apache.org/jira/browse/CALCITE-4951
 Project: Calcite
  Issue Type: Task
  Components: avatica
Reporter: Stamatis Zampetakis
Assignee: Stamatis Zampetakis
 Fix For: avatica-1.21.0


The [2.17.0 
release|https://logging.apache.org/log4j/2.x/changes-report.html#a2.17.0] fixes 
a new security vulnerability CVE-2021-45105.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (CALCITE-4950) Upgrade log4j2 version 2.17.0

[Stamatis Zampetakis (Jira)]

Stamatis Zampetakis created CALCITE-4950:


 Summary: Upgrade log4j2 version 2.17.0
 Key: CALCITE-4950
 URL: https://issues.apache.org/jira/browse/CALCITE-4950
 Project: Calcite
  Issue Type: Task
Reporter: Stamatis Zampetakis
Assignee: Stamatis Zampetakis
 Fix For: 1.29.0


The [2.17.0 
release|https://logging.apache.org/log4j/2.x/changes-report.html#a2.17.0] fixes 
a new security vulnerability CVE-2021-45105. Calcite is not impacted cause 
log4j2 is used only for testing purposes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Build failed in Jenkins: Calcite » Calcite-snapshots #22

[Apache Jenkins Server]

See 


Changes:

[Stamatis Zampetakis] [CALCITE-4704] Log plan on rule application using explain 
formatting


--
[...truncated 426.06 KB...]
< ++---+
< (1 row)
< 
---
> java.sql.SQLException: Error while executing SQL "select * from d10": 
From line 1, column 15 to line 1, column 17: Object 'D10' not found
>   at org.apache.calcite.avatica.Helper.createException(Helper.java:56)
>   at org.apache.calcite.avatica.Helper.createException(Helper.java:41)
>   at 
org.apache.calcite.avatica.AvaticaStatement.executeInternal(AvaticaStatement.java:163)
>   at 
org.apache.calcite.avatica.AvaticaStatement.executeQuery(AvaticaStatement.java:227)
>   at net.hydromatic.quidem.Quidem.checkResult(Quidem.java:325)
>   at net.hydromatic.quidem.Quidem.access$2800(Quidem.java:54)
>   at 
net.hydromatic.quidem.Quidem$ContextImpl.checkResult(Quidem.java:1748)
>   at 
net.hydromatic.quidem.Quidem$CheckResultCommand.execute(Quidem.java:1079)
>   at 
net.hydromatic.quidem.Quidem$CompositeCommand.execute(Quidem.java:1549)
>   at net.hydromatic.quidem.Quidem.execute(Quidem.java:216)
>   at org.apache.calcite.test.QuidemTest.checkRun(QuidemTest.java:171)
>   at org.apache.calcite.test.QuidemTest.test(QuidemTest.java:222)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
>   at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
>   at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
>   at 
org.junit.jupiter.engine.extension.TimeoutInvocation.proceed(TimeoutInvocation.java:46)
>   at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
>   at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
>   at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestTemplateMethod(TimeoutExtension.java:92)
>   at 
org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
>   at 
org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
>   at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
>   at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
>   at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
>   at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
>   at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
>   at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
>   at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:214)
>   at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
>   at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:210)
>   at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:135)
>   at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:66)
>   at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$6(NodeTestTask.java:151)
>   at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
>   at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
>   at 
org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
>   at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
>   at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
>   at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
>   at 
org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
>   at 

Re: [DISCUSS] State of the project 2021

[Stamatis Zampetakis]

Hi all,

Thanks a lot for serving as chair Haisheng and for preparing this nice
overview for 2021.

Indeed it was a good year; the community has grown with new contributors
and committers and the project has matured and evolved.

It's been quite some time since the last addition of a PMC member. I would
like to see our committers get more evolved with the project to eventually
join the PMC. More involved does not necessarily mean more commits/patches
but more interest about the wellbeing of the community and the future of
the project in general (participate in discussions, review work of others,
help newcomers, talk about Calcite in forums, etc).

As the previous years, we are still struggling to find reviewers and many
patches go stale. I don't have a solution to suggest but there have been
various discussions around this and I am positive that we will work out
something. I wanted to mention that we do value reviews from non-committers
and it would be nice to have them more often both for merging patches
faster but also for growing the community.

Another positive change of this year is the avatica project, which has
received a bit more attention compared to previous years, with people
helping to review/finalize patches and making releases. I hope we improve
even more on these aspects.
Last year many people mentioned that they would like to see Calcite handle
better materialized views and we did have many improvements on this domain
during 2021. We have the opportunity to take this one step further if we
manage to merge the work around the Tempura optimizer. The authors did try
a lot to get this in the codebase and we owe them a few reviews.

As the new PMC chair I strongly believe that Ruben is an excellent
candidate. He has been in the project for quite some time and knows well
how the community operates. Moreover, he has a strong technical background
and has pushed many important contributions in the repo.

Last, I would like to highlight that this discussion is open for all, and
not only members of the project. We would love to have feedback on all the
positive and negative aspects of this project so that we can improve it.

Best,
Stamatis


On Sat, Dec 18, 2021 at 3:22 AM Forward Xu  wrote:

> Thank you very much Ruben for his work.
>
> Ruben PMC chair +1
>
>
> Forwardxu
>
> Haisheng Yuan  于2021年12月11日周六 09:03写道：
>
> > Hi Calcite community members,
> >
> > It has been 6 years since Calcite graduated to a top level Apache
> project.
> > I am so excited to witness how vivid the community has become and how far
> > we have come.
> >
> > We have seen 2 releases so far for Calcite this year (with another
> release
> > v1.29.0 ongoing), with each release containing a large amount of changes.
> > Specifically, there are many new features introduced: the InnoDB Adaptor,
> > three-value logic for SEARCH operator, Enumerable MergeUnion operator,
> the
> > UNIQUE sub-query predicate... as well as the improvements to materialized
> > view recognition. We won't see Calcite's continuous improvements without
> > the community members' collaboration and dedication.
> >
> > In terms of Calcite Avatica, we had 2 releases for Avatica and 0 releases
> > for Avatica Go.  Avatica consistently has fewer contributors and pull
> > requests than Calcite, maybe because it has fewer users and the code
> hasn't
> > changed aggressively. But more contributors and code reviewers are highly
> > welcome and appreciated.
> >
> > I am glad to see that we had several technical meetups, not to mention at
> > ApacheCon and StangeLoop, to talk about the use cases and improvements
> that
> > we have done to Calcite. Many thanks to those who presented talks to give
> > more people opportunities to know and use Calcite, and more importantly,
> to
> > enrich the Calcite community.
> >
> > It's been a great privilege to be able to serve as Calcite's PMC chair in
> > 2021. It's also been a big learning experience for me and I am grateful
> to
> > those who trusted me and helped me in the journey. I am also extremely
> > proud of having this opportunity to work with Calcite contributors and
> > committers.
> >
> > Last but not least, we need to discuss who should be the new PMC chair of
> > Calcite after I step down in December. I would like to nominate Ruben
> > Quesada Lopez as the first candidate in the vote. Ruben has been a great
> > contributor to the project. He has shown a lot of care for the Calcite
> > project and the community, which I feel would make him a great PMC chair.
> >
> > To repeat questions from previous years:
> > 1) What else are we doing well in the project?
> > 2) What areas do we need to do better?
> >
> > Please take some time to share your thoughts!
> >
> > Thanks,
> > Haisheng
> >
>

Re: Committer permissions

[Stamatis Zampetakis]

Hi Vladimir,

You have already committers rights. As Duan mentioned, you probably need to
link your ASF with your GitHub account.

Check the instructions here:
https://calcite.apache.org/docs/howto.html#managing-calcite-repositories-through-github

Best,
Stamatis

On Sat, Dec 18, 2021 at 1:00 PM xiong duan  wrote:

> Hi Vladimir,
>
> I guess you need to set the Committer authority. Maybe can try
> https://gitbox.apache.org/setup/ to check your count.  It includes three
> procedures:
>
> 1) authority for Apache Count
> 2) authority for Github Count
> 3) authority for Apache Organization
>
>
> Vladimir Ozerov  于2021年12月18日周六 16:57写道：
>
> > Hi,
> >
> > It seems that I do not have the committer permissions to the repo, as I
> can
> > merge PR neither from GitHub, nor manually. Could you please grant me the
> > required access rights? Please let me know if any additional information
> is
> > required.
> >
> > Regards,
> > Vladimir.
> >
>

Re: Committer permissions

[xiong duan]

Hi Vladimir,

I guess you need to set the Committer authority. Maybe can try
https://gitbox.apache.org/setup/ to check your count.  It includes three
procedures:

1) authority for Apache Count
2) authority for Github Count
3) authority for Apache Organization


Vladimir Ozerov  于2021年12月18日周六 16:57写道：

> Hi,
>
> It seems that I do not have the committer permissions to the repo, as I can
> merge PR neither from GitHub, nor manually. Could you please grant me the
> required access rights? Please let me know if any additional information is
> required.
>
> Regards,
> Vladimir.
>

Re: [Calcite Release] Preparing for 1.29.0 Release

[Vladimir Ozerov]

Hi Xiong,

I've just resolved the conflicts.

Regards,
Vladimir.

сб, 18 дек. 2021 г. в 10:48, xiong duan :

> Hi, Vladimir.
>
> The PR[https://github.com/apache/calcite/pull/2464] looks good. If you
> have
> free time Please resolve the conflicts. Then we can merge it.
>
> Vladimir Ozerov  于2021年12月18日周六 15:20写道：
>
> > Hi,
> >
> > Could you please also merge
> > https://github.com/apache/calcite/pull/2464 ? I guess it got stuck
> > somehow,
> > as all the comments are addressed. This issue forced us to create a copy
> of
> > the AggregateUnionTransposeRule in our project.
> >
> > Regards,
> > Vladimir
> >
> > Сб, 18 дек. 2021 г. в 09:51, Rui Wang :
> >
> > > Thanks Julian!
> > >
> > > Now we will just decide whether to merge CALCITE-4907 or not, then I
> will
> > > lock the main branch and start the release process.
> > >
> > >
> > > -Rui
> > >
> > > On Fri, Dec 17, 2021 at 10:29 PM Julian Hyde 
> > > wrote:
> > >
> > > > Rui, I have merged CALCITE-4946.
> > > >
> > > > > On Dec 17, 2021, at 10:21 PM, Rui Wang 
> wrote:
> > > > >
> > > > > Thanks Zhe.
> > > > >
> > > > > Hi Francesco,
> > > > >
> > > > > I left a comment in your PR. Can you take a look?
> > > > >
> > > > > -Rui
> > > > >
> > > > > On Fri, Dec 17, 2021 at 3:32 PM Zhe Hu  wrote:
> > > > >
> > > > >> Hi, Rui.
> > > > >> CALCITE-4860 will be fixed in next release, you can pass it
> > currently.
> > > > >> Thanks for your work!
> > > > >>
> > > > >>
> > > > >> Best,
> > > > >> ZheHu
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >> On 12/18/2021 06:08，Francesco Gini
> wrote：
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4907 is in review.
> I
> > > > believe
> > > > >> I have addressed all the comments. Let me know if I missed
> anything.
> > > > >>
> > > > >> On Fri, 17 Dec 2021 at 22:42, Jacques Nadeau 
> > > > wrote:
> > > > >>
> > > > >> I've merged CALCITE-4948 to mitigate the concerns around
> > CALCITE-4898
> > > > and
> > > > >> maven repositories and category x licenses.
> > > > >>
> > > > >> On Fri, Dec 17, 2021 at 1:02 PM Rui Wang 
> > > wrote:
> > > > >>
> > > > >> For the list of 1.29 fix Jira, several Jira have been marked as
> > > resolved
> > > > >> since this Monday. I will do another pass today but probably not
> all
> > > > >> those
> > > > >> will make the 1.29.0 release.
> > > > >>
> > > > >>
> > > > >> -Rui
> > > > >>
> > > > >> On Fri, Dec 17, 2021 at 11:57 AM Ruben Q L 
> > wrote:
> > > > >>
> > > > >> Hello,
> > > > >>
> > > > >> FYI https://issues.apache.org/jira/browse/CALCITE-4737 has been
> > > > >> merged.
> > > > >>
> > > > >> Regards,
> > > > >> Ruben
> > > > >>
> > > > >>
> > > > >> On Fri, Dec 17, 2021 at 7:40 PM Julian Hyde <
> jhyde.apa...@gmail.com
> > >
> > > > >> wrote:
> > > > >>
> > > > >> Rui,
> > > > >>
> > > > >> Even though https://issues.apache.org/jira/browse/CALCITE-4898 <
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4898> is marked
> > fixed,
> > > > >> there’s some fallout regarding maven repositories and category X.
> > > > >> That
> > > > >> needs to be sorted out before RC0. See [1].
> > > > >>
> > > > >> I’m working on getting
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4946
> > > > >>  done today.
> > > > >> Please
> > > > >> wait for that.
> > > > >>
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4885 <
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4885> is a big
> > > > >> refactoring
> > > > >> and, though I’d love to get it in before the release, it isn’t
> going
> > > > >> to
> > > > >> happen. Don’t wait for it.
> > > > >>
> > > > >> I also see the following as open or in progress and fix-in-1.29:
> > > > >> * https://issues.apache.org/jira/browse/CALCITE-4872 <
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4872> (Will Noble)
> > > > >> * https://issues.apache.org/jira/browse/CALCITE-4908 <
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4908> (Woonsan Koo)
> > > > >> * https://issues.apache.org/jira/browse/CALCITE-4704 <
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4704> (Stamatis)
> > > > >> * https://issues.apache.org/jira/browse/CALCITE-4737 <
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4737> (Thomas
> Rebele)
> > > > >> * https://issues.apache.org/jira/browse/CALCITE-4860 <
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4860> (Zhe Hu /
> Duan
> > > > >> Xiong)
> > > > >> * https://issues.apache.org/jira/browse/CALCITE-4907 <
> > > > >> https://issues.apache.org/jira/browse/CALCITE-4907> (Francesco
> > Gini)
> > > > >>
> > > > >> What’s the status on those?
> > > > >>
> > > > >> Julian
> > > > >>
> > > > >> [1] https://github.com/apache/calcite/pull/2622 <
> > > > >> https://github.com/apache/calcite/pull/2622>
> > > > >>
> > > > >> PS It feels churlish to bring this up, but in time-honored
> tradition
> > > > >> the
> > > > >> email subject has been ‘[DISCUSS] Towards Calcite x.y.z’.
> > > 

Committer permissions

[Vladimir Ozerov]

Hi,

It seems that I do not have the committer permissions to the repo, as I can
merge PR neither from GitHub, nor manually. Could you please grant me the
required access rights? Please let me know if any additional information is
required.

Regards,
Vladimir.