Re: [ANNOUNCE] New committer: Danny Chan

2019-05-14 Thread Enrico Olivelli
Congratulations!

Enrico

Il mer 15 mag 2019, 04:11 Rong Rong  ha scritto:

> Congratulations Danny!
>
> On Tue, May 14, 2019 at 2:45 PM Stamatis Zampetakis 
> wrote:
>
> > Congrats Danny, and thanks a lot for all the effort you are putting in
> > helping others and improving Calcite.
> >
> > Among so many high quality contributions it is difficult to express
> > preferences, nevertheless I think your work on
> > n implicit type casting (CALCITE-2302) is going to benefit many people.
> >
> > Welcome and keep up the good work.
> >
> > Best,
> > Stamatis
> >
> >
> > On Tue, May 14, 2019, 9:01 PM Andrei Sereda  wrote:
> >
> > > Congratulations!
> > >
> > > On Tue, May 14, 2019 at 10:14 AM Michael Mior 
> wrote:
> > >
> > > > Congratulations and thank you Danny!
> > > > --
> > > > Michael Mior
> > > > mm...@apache.org
> > > >
> > > > Le lun. 13 mai 2019 à 21:57, Yuzhao Chen  a
> > écrit
> > > :
> > > > >
> > > > > Thank you everyone for your kind messages.
> > > > >
> > > > > Currently I am working in Alibaba Blink SQL Engine team in
> Hangzhou,
> > > > Zhejiang, China. We are developing a production version of Apache
> > Flink.
> > > > Our team has done many promotions for flink-table module and recently
> > we
> > > > are merging and contributing our codebase to the Apache Flink
> > community.
> > > > >
> > > > > It is my honor to be part of Apache Calcite community, I will
> > > contribute
> > > > continuously to this great project.
> > > > >
> > > > > Best,
> > > > > Danny Chan
> > > > > 在 2019年5月14日 +0800 AM6:40,Francis Chuang  > > >,写道:
> > > > > > Apache Calcite's Project Management Committee (PMC) has invited
> > Danny
> > > > > > Chan to become a committer, and we are pleased to announce that
> he
> > > has
> > > > > > accepted.
> > > > > >
> > > > > > Danny has been a prolific contributor to Calcite, with
> CALCITE-2969
> > > > > > being one of his more complex contributions to date. He has also
> > been
> > > > > > extremely active on our mailing lists, contributing to many
> design
> > > > > > discussions.
> > > > > >
> > > > > > Danny, welcome, thank you for your contributions, and we look
> > forward
> > > > > > your further interactions with the community! If you wish, please
> > > feel
> > > > > > free to tell us more about yourself and what you are working on.
> > > > > >
> > > > > > Francis (on behalf of the Apache Calcite PMC)
> > > >
> > >
> >
>


[jira] [Created] (CALCITE-3067) Splunk Calcite adapter cannot parse the right session key from Splunk 7.2

2019-05-14 Thread Shawn Chen (JIRA)
Shawn Chen created CALCITE-3067:
---

 Summary: Splunk Calcite adapter cannot parse the right session key 
from Splunk 7.2
 Key: CALCITE-3067
 URL: https://issues.apache.org/jira/browse/CALCITE-3067
 Project: Calcite
  Issue Type: Bug
  Components: splunk
Affects Versions: 1.19.0
 Environment: Splunk 7.2 on Mac OS 10.14

Calcite 1.19
Reporter: Shawn Chen
 Fix For: next


SplunkConnectionImpl.java successfully builds a connection to Splunk 7.2, but 
it cannot parse the correct session key due to the outdated regular expression. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


Re: [ANNOUNCE] New committer: Danny Chan

2019-05-14 Thread Rong Rong
Congratulations Danny!

On Tue, May 14, 2019 at 2:45 PM Stamatis Zampetakis 
wrote:

> Congrats Danny, and thanks a lot for all the effort you are putting in
> helping others and improving Calcite.
>
> Among so many high quality contributions it is difficult to express
> preferences, nevertheless I think your work on
> n implicit type casting (CALCITE-2302) is going to benefit many people.
>
> Welcome and keep up the good work.
>
> Best,
> Stamatis
>
>
> On Tue, May 14, 2019, 9:01 PM Andrei Sereda  wrote:
>
> > Congratulations!
> >
> > On Tue, May 14, 2019 at 10:14 AM Michael Mior  wrote:
> >
> > > Congratulations and thank you Danny!
> > > --
> > > Michael Mior
> > > mm...@apache.org
> > >
> > > Le lun. 13 mai 2019 à 21:57, Yuzhao Chen  a
> écrit
> > :
> > > >
> > > > Thank you everyone for your kind messages.
> > > >
> > > > Currently I am working in Alibaba Blink SQL Engine team in Hangzhou,
> > > Zhejiang, China. We are developing a production version of Apache
> Flink.
> > > Our team has done many promotions for flink-table module and recently
> we
> > > are merging and contributing our codebase to the Apache Flink
> community.
> > > >
> > > > It is my honor to be part of Apache Calcite community, I will
> > contribute
> > > continuously to this great project.
> > > >
> > > > Best,
> > > > Danny Chan
> > > > 在 2019年5月14日 +0800 AM6:40,Francis Chuang  > >,写道:
> > > > > Apache Calcite's Project Management Committee (PMC) has invited
> Danny
> > > > > Chan to become a committer, and we are pleased to announce that he
> > has
> > > > > accepted.
> > > > >
> > > > > Danny has been a prolific contributor to Calcite, with CALCITE-2969
> > > > > being one of his more complex contributions to date. He has also
> been
> > > > > extremely active on our mailing lists, contributing to many design
> > > > > discussions.
> > > > >
> > > > > Danny, welcome, thank you for your contributions, and we look
> forward
> > > > > your further interactions with the community! If you wish, please
> > feel
> > > > > free to tell us more about yourself and what you are working on.
> > > > >
> > > > > Francis (on behalf of the Apache Calcite PMC)
> > >
> >
>


Re: [ANNOUNCE] New committer: Danny Chan

2019-05-14 Thread Stamatis Zampetakis
Congrats Danny, and thanks a lot for all the effort you are putting in
helping others and improving Calcite.

Among so many high quality contributions it is difficult to express
preferences, nevertheless I think your work on
n implicit type casting (CALCITE-2302) is going to benefit many people.

Welcome and keep up the good work.

Best,
Stamatis


On Tue, May 14, 2019, 9:01 PM Andrei Sereda  wrote:

> Congratulations!
>
> On Tue, May 14, 2019 at 10:14 AM Michael Mior  wrote:
>
> > Congratulations and thank you Danny!
> > --
> > Michael Mior
> > mm...@apache.org
> >
> > Le lun. 13 mai 2019 à 21:57, Yuzhao Chen  a écrit
> :
> > >
> > > Thank you everyone for your kind messages.
> > >
> > > Currently I am working in Alibaba Blink SQL Engine team in Hangzhou,
> > Zhejiang, China. We are developing a production version of Apache Flink.
> > Our team has done many promotions for flink-table module and recently we
> > are merging and contributing our codebase to the Apache Flink community.
> > >
> > > It is my honor to be part of Apache Calcite community, I will
> contribute
> > continuously to this great project.
> > >
> > > Best,
> > > Danny Chan
> > > 在 2019年5月14日 +0800 AM6:40,Francis Chuang  >,写道:
> > > > Apache Calcite's Project Management Committee (PMC) has invited Danny
> > > > Chan to become a committer, and we are pleased to announce that he
> has
> > > > accepted.
> > > >
> > > > Danny has been a prolific contributor to Calcite, with CALCITE-2969
> > > > being one of his more complex contributions to date. He has also been
> > > > extremely active on our mailing lists, contributing to many design
> > > > discussions.
> > > >
> > > > Danny, welcome, thank you for your contributions, and we look forward
> > > > your further interactions with the community! If you wish, please
> feel
> > > > free to tell us more about yourself and what you are working on.
> > > >
> > > > Francis (on behalf of the Apache Calcite PMC)
> >
>


Re: a new adapter for Apache Kafka

2019-05-14 Thread Julian Hyde
> Do you feel comfortable with Kafka adapter being part of calcite main 
> codebase ? 

+1

I don’t think we need a formal vote. There seems to be consensus that we want 
this. We need to get it through the code review process, and I’m sure we can. 
Andrei has already done a great job reviewing line-by-line.

I have made high-level comments in 
https://issues.apache.org/jira/browse/CALCITE-2913 
. JIRA is better than 
GitHub for high-level review (questions such as “How is a release manager going 
to test this before each release?”)

Julian


> On May 14, 2019, at 11:56 AM, Andrei Sereda  wrote:
> 
> Hello,
> 
> I have reviewed the PR and it mostly looks good. There are some small
> things left, but no blockers.
> 
> Do you feel comfortable with Kafka adapter being part of calcite main
> codebase ?  Is there anybody against merging proposed PR ?
> 
> Regards.
> 
> On Thu, May 9, 2019 at 2:36 PM Mingmin Xu  wrote:
> 
>> Thank you Andrei, appreciated for your time.
>> 
>> On Thu, May 9, 2019 at 11:29 AM Andrei Sereda  wrote:
>> 
>>> Mingmin, I'll be reviewing the PR this week.
>>> Sorry was busy last couple of weeks.
>>> 
>>> On Thu, May 9, 2019 at 12:54 PM Mingmin Xu  wrote:
>>> 
 Quick ping ~~~
 Can someone take a look at this PR(1)? I suppose a Kafka adapter will
>> be
 very helpful to accelerate the adoption of Calcite Stream SQL.
 
 [1]. https://github.com/apache/calcite/pull/1127
 
 Mingmin
 
 On Wed, Apr 24, 2019 at 11:31 PM Mingmin Xu 
>> wrote:
 
> Thank you @Andrei @Michael. Currently it's a straightforward
> implementation of stream ScannableTable, a site page is added for
>>> usage.
> Kindly let me know if something important is not covered.
> 
> Mingmin
> 
> On Wed, Apr 24, 2019 at 1:24 PM Michael Mior 
>> wrote:
> 
>> I think we'd generally be willing to accept any adapter which is
>> well-written, well-tested, and likely to be generally useful. I
>> think
>> Kafka meets the final criterion and with some work the current code
>> could meet the first two. That said, even if the adapter isn't
>> accepted into the main Calcite codebase, I would encourage you to
>> publish it as a separate package anyway.
>> --
>> Michael Mior
>> mm...@apache.org
>> 
>> Le mer. 24 avr. 2019 à 08:07, Andrei Sereda  a
>>> écrit
 :
>>> 
>>> Hi Mingmin,
>>> 
>>> I'm happy to review it.
>>> 
>>> Before would like to confirm with this list that they're OK adding
>>> new
>>> adapter (kafka) to calcite codebase ?
>>> 
>>> Regards,
>>> Andrei.
>>> 
>>> On Tue, Apr 23, 2019 at 10:43 PM Mingmin Xu 
 wrote:
>>> 
 Hi all,
 
 I add a new adapter for Apache Kafka, to allow users to query
>>> Kafka
>> topics
 with Calcite STREAM SQL. Can someone take a look at the PR[1]?
 
 [1]. https://github.com/apache/calcite/pull/1127
 
 Thanks!
 Mingmin
 
>> 
> 
> 
> --
> 
> Mingmin
> 
 
 
 --
 
 Mingmin
 
>>> 
>> 
>> 
>> --
>> 
>> Mingmin
>> 



Re: [VOTE] Release apache-calcite-avatica-go-4.0.0 (release candidate 1)

2019-05-14 Thread Kevin Risden
+1 (binding)

macOS 10.14.3
* Checked hashes and signatures
* Release notes look good
* Tests run in docker for both git hash and tar.gz

Kevin Risden


On Tue, May 14, 2019 at 5:07 AM Stamatis Zampetakis 
wrote:

> Windows 10 Pro, jdk1.8.0_202, Docker Community 18.09.2
> * Checked signatures and checksums OK
> * Went over release note OK
> * Run tests (docker-compose run test) on git repo OK
>
> (Minor comment) I noticed that in the release note there is (at least) an
> entry (i.e., CALCITE-3024) where the description does not match exactly the
> Jira summary or the commit message.
> Since there are also cases that the commit message is not the same with the
> Jira summary, I was wondering (mostly for future releases) what we are
> supposed to put in the release note.
> Let's discuss this if necessary in a separate thread.
>
> +1 (binding)
>
> On Sun, May 12, 2019 at 2:04 PM Francis Chuang 
> wrote:
>
> > Hi all,
> >
> > I have created a release for Apache Calcite Avatica Go 4.0.0, release
> > candidate 1.
> >
> > Thanks to everyone who has contributed to this release. The release
> > notes are available here:
> >
> >
> https://github.com/apache/calcite-avatica-go/blob/3790ef528d63d9c274114f8d21fc6c6003ef8bcf/site/_docs/go_history.md
> >
> > The commit to be voted on:
> >
> >
> https://gitbox.apache.org/repos/asf?p=calcite-avatica-go.git;a=commit;h=3790ef528d63d9c274114f8d21fc6c6003ef8bcf
> >
> > The hash is 3790ef528d63d9c274114f8d21fc6c6003ef8bcf
> >
> > The artifacts to be voted on are located here:
> >
> >
> https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-go-4.0.0-rc1/
> >
> > The hashes of the artifacts are as follows:
> > src.tar.gz FDDFD5F8 6386A748 5308532A 56CD2836 220E2CE8 A00955DC
> > 6E5E9315 45813C57 4B03FA1C 17008C19 981C07EE 4CAC9391 2CFEB06C DDBA8D9A
> > F1E36218 03C46063
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/francischuang.asc
> >
> > Instructions for running the test suite is located here:
> >
> >
> https://github.com/apache/calcite-avatica-go/blob/3790ef528d63d9c274114f8d21fc6c6003ef8bcf/site/develop/avatica-go.md#testing
> >
> > Please vote on releasing this package as Apache Calcite Avatica Go 4.0.0.
> >
> > To run the tests without a Go environment, install docker and
> > docker-compose. Then, in the root of the release's directory, run:
> > docker-compose run test
> >
> > When the test suite completes, run "docker-compose down" to remove and
> > shutdown all the containers.
> >
> > The vote is open for the next 72 hours and passes if a majority of at
> > least three +1 PMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Calcite Avatica Go 4.0.0
> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> >
> > Here is my vote:
> >
> > +1 (binding)
> >
> > Francis
> >
>


Re: [ANNOUNCE] New committer: Danny Chan

2019-05-14 Thread Andrei Sereda
Congratulations!

On Tue, May 14, 2019 at 10:14 AM Michael Mior  wrote:

> Congratulations and thank you Danny!
> --
> Michael Mior
> mm...@apache.org
>
> Le lun. 13 mai 2019 à 21:57, Yuzhao Chen  a écrit :
> >
> > Thank you everyone for your kind messages.
> >
> > Currently I am working in Alibaba Blink SQL Engine team in Hangzhou,
> Zhejiang, China. We are developing a production version of Apache Flink.
> Our team has done many promotions for flink-table module and recently we
> are merging and contributing our codebase to the Apache Flink community.
> >
> > It is my honor to be part of Apache Calcite community, I will contribute
> continuously to this great project.
> >
> > Best,
> > Danny Chan
> > 在 2019年5月14日 +0800 AM6:40,Francis Chuang ,写道:
> > > Apache Calcite's Project Management Committee (PMC) has invited Danny
> > > Chan to become a committer, and we are pleased to announce that he has
> > > accepted.
> > >
> > > Danny has been a prolific contributor to Calcite, with CALCITE-2969
> > > being one of his more complex contributions to date. He has also been
> > > extremely active on our mailing lists, contributing to many design
> > > discussions.
> > >
> > > Danny, welcome, thank you for your contributions, and we look forward
> > > your further interactions with the community! If you wish, please feel
> > > free to tell us more about yourself and what you are working on.
> > >
> > > Francis (on behalf of the Apache Calcite PMC)
>


Re: a new adapter for Apache Kafka

2019-05-14 Thread Andrei Sereda
Hello,

I have reviewed the PR and it mostly looks good. There are some small
things left, but no blockers.

Do you feel comfortable with Kafka adapter being part of calcite main
codebase ?  Is there anybody against merging proposed PR ?

Regards.

On Thu, May 9, 2019 at 2:36 PM Mingmin Xu  wrote:

> Thank you Andrei, appreciated for your time.
>
> On Thu, May 9, 2019 at 11:29 AM Andrei Sereda  wrote:
>
> > Mingmin, I'll be reviewing the PR this week.
> > Sorry was busy last couple of weeks.
> >
> > On Thu, May 9, 2019 at 12:54 PM Mingmin Xu  wrote:
> >
> > > Quick ping ~~~
> > > Can someone take a look at this PR(1)? I suppose a Kafka adapter will
> be
> > > very helpful to accelerate the adoption of Calcite Stream SQL.
> > >
> > > [1]. https://github.com/apache/calcite/pull/1127
> > >
> > > Mingmin
> > >
> > > On Wed, Apr 24, 2019 at 11:31 PM Mingmin Xu 
> wrote:
> > >
> > > > Thank you @Andrei @Michael. Currently it's a straightforward
> > > > implementation of stream ScannableTable, a site page is added for
> > usage.
> > > > Kindly let me know if something important is not covered.
> > > >
> > > > Mingmin
> > > >
> > > > On Wed, Apr 24, 2019 at 1:24 PM Michael Mior 
> wrote:
> > > >
> > > >> I think we'd generally be willing to accept any adapter which is
> > > >> well-written, well-tested, and likely to be generally useful. I
> think
> > > >> Kafka meets the final criterion and with some work the current code
> > > >> could meet the first two. That said, even if the adapter isn't
> > > >> accepted into the main Calcite codebase, I would encourage you to
> > > >> publish it as a separate package anyway.
> > > >> --
> > > >> Michael Mior
> > > >> mm...@apache.org
> > > >>
> > > >> Le mer. 24 avr. 2019 à 08:07, Andrei Sereda  a
> > écrit
> > > :
> > > >> >
> > > >> > Hi Mingmin,
> > > >> >
> > > >> > I'm happy to review it.
> > > >> >
> > > >> > Before would like to confirm with this list that they're OK adding
> > new
> > > >> > adapter (kafka) to calcite codebase ?
> > > >> >
> > > >> > Regards,
> > > >> > Andrei.
> > > >> >
> > > >> > On Tue, Apr 23, 2019 at 10:43 PM Mingmin Xu 
> > > wrote:
> > > >> >
> > > >> > > Hi all,
> > > >> > >
> > > >> > > I add a new adapter for Apache Kafka, to allow users to query
> > Kafka
> > > >> topics
> > > >> > > with Calcite STREAM SQL. Can someone take a look at the PR[1]?
> > > >> > >
> > > >> > > [1]. https://github.com/apache/calcite/pull/1127
> > > >> > >
> > > >> > > Thanks!
> > > >> > > Mingmin
> > > >> > >
> > > >>
> > > >
> > > >
> > > > --
> > > > 
> > > > Mingmin
> > > >
> > >
> > >
> > > --
> > > 
> > > Mingmin
> > >
> >
>
>
> --
> 
> Mingmin
>


Re: Placeholder schema for Volcano planner

2019-05-14 Thread Ivan Grgurina
Resending





From: Ivan Grgurina 
Sent: Tuesday, May 14, 2019 1:52 PM
To: dev@calcite.apache.org
Subject: Placeholder schema for Volcano planner

Hi everyone, I've managed to make some progress on my master thesis project
since last time we spoke [1]. I used a model.json configuration custom
schema factory to add rules and that worked, rules got executed, just not
chosen as the best option. You can find the code here: [2]. Now my
questions are:

1) Can I tell Volcano planner to ignore 1 out of 3 schemas that I passed
through custom JDBC SchemaFactory?

*I want parser to work on that 1 original schema*, but for the planner to
never suggest an optimal (cheapest) plan in that schema (only other 2
derived schemas). 1 original schema is always mapped 1-to-1 with other 2
derived schemas, so the RelNode that my rule returns is always semantically
equivalent, just more expensive (security reasons).

2) If that can't work, how can I call HepPlanner instead of default Volcano
planner *from SchemaFactory *that is set in model.json, since that's my
starting point?

3) Ideally, I would have HepPlanner execute my rules that transform them to
semantically equivalent expressions that use 2 derived schemas instead of 1
original schema (I have a rules that do that), and then have Volcano
planner optimize that using *only* 2 derived schemas, without having an
idea that 1 original schema exists, due to security reasons.

Unfortunately, I have no idea how to do that. Any help would be appreciated
:)

[1]
http://mail-archives.apache.org/mod_mbox/calcite-dev/201905.mbox/%3cam6pr08mb5061442901dbfe49ed43329a92...@am6pr08mb5061.eurprd08.prod.outlook.com%3E
[2] https://github.com/igrgurina/multicloud_rewriter


Re: [ANNOUNCE] New committer: Danny Chan

2019-05-14 Thread Michael Mior
Congratulations and thank you Danny!
--
Michael Mior
mm...@apache.org

Le lun. 13 mai 2019 à 21:57, Yuzhao Chen  a écrit :
>
> Thank you everyone for your kind messages.
>
> Currently I am working in Alibaba Blink SQL Engine team in Hangzhou, 
> Zhejiang, China. We are developing a production version of Apache Flink. Our 
> team has done many promotions for flink-table module and recently we are 
> merging and contributing our codebase to the Apache Flink community.
>
> It is my honor to be part of Apache Calcite community, I will contribute 
> continuously to this great project.
>
> Best,
> Danny Chan
> 在 2019年5月14日 +0800 AM6:40,Francis Chuang ,写道:
> > Apache Calcite's Project Management Committee (PMC) has invited Danny
> > Chan to become a committer, and we are pleased to announce that he has
> > accepted.
> >
> > Danny has been a prolific contributor to Calcite, with CALCITE-2969
> > being one of his more complex contributions to date. He has also been
> > extremely active on our mailing lists, contributing to many design
> > discussions.
> >
> > Danny, welcome, thank you for your contributions, and we look forward
> > your further interactions with the community! If you wish, please feel
> > free to tell us more about yourself and what you are working on.
> >
> > Francis (on behalf of the Apache Calcite PMC)


Re: [ANNOUNCE] New committer: Danny Chan

2019-05-14 Thread Kevin Risden
Welcome and congrats!

Kevin Risden


On Tue, May 14, 2019 at 1:27 AM Lin Li  wrote:

> Congratulations, Danny!
>
> Best,
> Lincoln
>
> Jark Wu  于2019年5月14日周二 上午10:05写道:
>
> > Congratulations Danny!
> >
> > Best,
> > Jark
> >
> > On Tue, 14 May 2019 at 09:57, Yuzhao Chen  wrote:
> >
> > > Thank you everyone for your kind messages.
> > >
> > > Currently I am working in Alibaba Blink SQL Engine team in Hangzhou,
> > > Zhejiang, China. We are developing a production version of Apache
> Flink.
> > > Our team has done many promotions for flink-table module and recently
> we
> > > are merging and contributing our codebase to the Apache Flink
> community.
> > >
> > > It is my honor to be part of Apache Calcite community, I will
> contribute
> > > continuously to this great project.
> > >
> > > Best,
> > > Danny Chan
> > > 在 2019年5月14日 +0800 AM6:40,Francis Chuang  >,写道:
> > > > Apache Calcite's Project Management Committee (PMC) has invited Danny
> > > > Chan to become a committer, and we are pleased to announce that he
> has
> > > > accepted.
> > > >
> > > > Danny has been a prolific contributor to Calcite, with CALCITE-2969
> > > > being one of his more complex contributions to date. He has also been
> > > > extremely active on our mailing lists, contributing to many design
> > > > discussions.
> > > >
> > > > Danny, welcome, thank you for your contributions, and we look forward
> > > > your further interactions with the community! If you wish, please
> feel
> > > > free to tell us more about yourself and what you are working on.
> > > >
> > > > Francis (on behalf of the Apache Calcite PMC)
> > >
> >
>


Placeholder schema for Volcano planner

2019-05-14 Thread Ivan Grgurina
Hi everyone, I've managed to make some progress on my master thesis project
since last time we spoke [1]. I used a model.json configuration custom
schema factory to add rules and that worked, rules got executed, just not
chosen as the best option. You can find the code here: [2]. Now my
questions are:

1) Can I tell Volcano planner to ignore 1 out of 3 schemas that I passed
through custom JDBC SchemaFactory?

*I want parser to work on that 1 original schema*, but for the planner to
never suggest an optimal (cheapest) plan in that schema (only other 2
derived schemas). 1 original schema is always mapped 1-to-1 with other 2
derived schemas, so the RelNode that my rule returns is always semantically
equivalent, just more expensive (security reasons).

2) If that can't work, how can I call HepPlanner instead of default Volcano
planner *from SchemaFactory *that is set in model.json, since that's my
starting point?

3) Ideally, I would have HepPlanner execute my rules that transform them to
semantically equivalent expressions that use 2 derived schemas instead of 1
original schema (I have a rules that do that), and then have Volcano
planner optimize that using *only* 2 derived schemas, without having an
idea that 1 original schema exists, due to security reasons.

Unfortunately, I have no idea how to do that. Any help would be appreciated
:)

[1]
http://mail-archives.apache.org/mod_mbox/calcite-dev/201905.mbox/%3cam6pr08mb5061442901dbfe49ed43329a92...@am6pr08mb5061.eurprd08.prod.outlook.com%3E
[2] https://github.com/igrgurina/multicloud_rewriter


Re: [VOTE] Release apache-calcite-avatica-go-4.0.0 (release candidate 1)

2019-05-14 Thread Stamatis Zampetakis
Windows 10 Pro, jdk1.8.0_202, Docker Community 18.09.2
* Checked signatures and checksums OK
* Went over release note OK
* Run tests (docker-compose run test) on git repo OK

(Minor comment) I noticed that in the release note there is (at least) an
entry (i.e., CALCITE-3024) where the description does not match exactly the
Jira summary or the commit message.
Since there are also cases that the commit message is not the same with the
Jira summary, I was wondering (mostly for future releases) what we are
supposed to put in the release note.
Let's discuss this if necessary in a separate thread.

+1 (binding)

On Sun, May 12, 2019 at 2:04 PM Francis Chuang 
wrote:

> Hi all,
>
> I have created a release for Apache Calcite Avatica Go 4.0.0, release
> candidate 1.
>
> Thanks to everyone who has contributed to this release. The release
> notes are available here:
>
> https://github.com/apache/calcite-avatica-go/blob/3790ef528d63d9c274114f8d21fc6c6003ef8bcf/site/_docs/go_history.md
>
> The commit to be voted on:
>
> https://gitbox.apache.org/repos/asf?p=calcite-avatica-go.git;a=commit;h=3790ef528d63d9c274114f8d21fc6c6003ef8bcf
>
> The hash is 3790ef528d63d9c274114f8d21fc6c6003ef8bcf
>
> The artifacts to be voted on are located here:
>
> https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-go-4.0.0-rc1/
>
> The hashes of the artifacts are as follows:
> src.tar.gz FDDFD5F8 6386A748 5308532A 56CD2836 220E2CE8 A00955DC
> 6E5E9315 45813C57 4B03FA1C 17008C19 981C07EE 4CAC9391 2CFEB06C DDBA8D9A
> F1E36218 03C46063
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/francischuang.asc
>
> Instructions for running the test suite is located here:
>
> https://github.com/apache/calcite-avatica-go/blob/3790ef528d63d9c274114f8d21fc6c6003ef8bcf/site/develop/avatica-go.md#testing
>
> Please vote on releasing this package as Apache Calcite Avatica Go 4.0.0.
>
> To run the tests without a Go environment, install docker and
> docker-compose. Then, in the root of the release's directory, run:
> docker-compose run test
>
> When the test suite completes, run "docker-compose down" to remove and
> shutdown all the containers.
>
> The vote is open for the next 72 hours and passes if a majority of at
> least three +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Calcite Avatica Go 4.0.0
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
>
> Here is my vote:
>
> +1 (binding)
>
> Francis
>