Hey Logan,
Many parts of Calcite such as rules and metadata providers rely on the
assumption that the RelNode tree does not contain subqueries. This is
achieved by using the SubQueryRemoveRule [1] early on during the
optimization process. Another pretty common preprocessing step is
query
Ubuntu 20.04.6 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 7.6.1
* Checked signatures and checksums OK
* Checked diff between repo and artifacts OK
* Checked README, NOTICE, LICENSE OK
* All source files have ASF headers OK ( grep -RiL "Licensed to the
Apache Software Foundation")
* No
Ubuntu 20.04.6 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 7.6.1
* Checked signatures and checksums OK
* Checked diff between repo and artifacts OK
* Went over release note OK (Left comments in the PR)
* Checked README, NOTICE, LICENSE OK
* All source files have ASF headers OK (raised [1] for
Stamatis Zampetakis created CALCITE-6385:
Summary: LintTest fails when run in source distribution
Key: CALCITE-6385
URL: https://issues.apache.org/jira/browse/CALCITE-6385
Project: Calcite
Stamatis Zampetakis created CALCITE-6384:
Summary: Missing ASF header from buildcache.yml,
gradle-wrapper-validation.yml
Key: CALCITE-6384
URL: https://issues.apache.org/jira/browse/CALCITE-6384
Regarding the additional joins, I think Calcite's Correlate [1] is the
equivalent of the dependent/binding join that appears in the database
literature. Currently, Correlate does not extend Join but we could
possibly reconsider this decision if necessary.
Best,
Stamatis
[1]
>>>>>>>>> Alessandro
> > >>>>>>>>>
> > >>>>>>>>> On Wed, 6 Mar 2024 at 16:49, Sergey Nuyanzin <
> > snuyan...@gmail.com>
> > >>>>>> wrote:
> > >>>>>>>>>
>
Hey Anurag,
The bucket error seems somewhat related to the Gradle caches [1, 2].
Try to disable the cache [3] to see if the error goes away.
The fact that the build gets stuck while running tests may require
further investigation and I guess it is strongly related to your
environment since
+1, nothing to add!
On Wed, Apr 3, 2024 at 11:11 PM Francis Chuang wrote:
>
> +1, Great work, Benchao!
>
> On 4/04/2024 5:39 am, Ruben Q L wrote:
> > +1
> >
> > Thanks Benchao for preparing the report!
> >
> >
> > On Wed, Apr 3, 2024 at 7:34 PM Michael Mior wrote:
> >
> >> +1 Thanks Benchao!
>
Ubuntu 20.04.6 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 8.1.1
* Checked signatures and checksums OK
* Checked diff between repo and artifacts OK
* Went over release note OK (It mentions two Gradle versions 8.4 and 8.5)
* Checked README, NOTICE, LICENSE OK (minor fixes in LICENSE from
Calcite
Congratulations Sergey, very well deserved!
On Wed, Mar 6, 2024 at 3:33 AM Hongyu Guo wrote:
>
> Congrats Sergey!
>
> Hongyu Guo
>
> On Wed, Mar 6, 2024 at 10:01 AM Jiajun Xie
> wrote:
>
> > Congratulations, Sergey!
> >
> > On Wed, 6 Mar 2024 at 09:43, Cancai Cai wrote:
> >
> > >
The Quidem approach definitely makes sense.
Alternatively, since we are focusing on the behavior of functions with
certain inputs it may be simpler to go with a Java parameterized test
backed by a CSV/JSON file ([1] outlines the general idea).
As others mentioned, using the org.testcontainers
With so many commits it's definitely a good time to cut a new release.
I can be the RM for 1.39.0 or 1.40.0 depending on the timing.
Best,
Stamatis
On Wed, Feb 21, 2024 at 12:10 AM Sergey Nuyanzin wrote:
>
> Thanks for starting the discussion
>
> > @Sergey, are you still available for being
The TableFunctionScan indeed seems to fit exactly the "FunctionJoin"
use-case. If the TableFunctionScan alone cannot fulfil your use-case
then I am pretty sure that a combination of Correlate +
TableFunctionScan should do the trick. The examples in the Calcite
codebase are a bit scarce but you can
Hey Eric,
EnumerabeProject and EnumerableFilter are not meant to appear in the
plan because they cannot be implemented; as you observed the implement
method throws an exception. For this reason it does not make sense to
use ENUMERABLE_PROJECT_RULE and ENUMERABLE_FILTER_RULE and this is why
the
Having a gradle task to ensure that class files are valid bytecode
seems like a good idea. It may not be 100% bulletproof since we yet
rely on another tool/library to perform the verification but still
having an extra check will not hurt if it is lightweight.
It makes sense to enforce a certain
Looks good thanks for putting it together Benchao!
On Fri, Jan 5, 2024 at 2:41 PM Benchao Li wrote:
>
> Hello,
>
> Below you can find a draft of this quarter's board report. I plan to
> submit the final version next Tuesday (Jan 9, 2024).
>
> Please let me know if you have any additions or
Hey Eric,
When you have a disjunction in the WHERE clause it may not be safe to
push the condition below a join especially when it comes to outer
joins. I suppose that the FilterJoinRule [1] is the place that you
want to check to see if the filter can be pushed below the join and
into the scan.
Hello,
I would say that the default rules are those tested to work well when
Calcite is used as an application through the various adapters etc. If
you are using Calcite as a library for building a new query planner
for another system then you should probably pick the rules from
scratch based on
The presence of the "minor" keyword in the commit summary is a bit
redundant. I would argue that if the message is precise enough the
person reading it can infer it is minor or not.
Moreover, the minor classification is subjective. Some people consider
minor things that do not change code at all.
Calcite community members,
I am pleased to announce that we have a new PMC chair and VP as per
our tradition of rotating the chair once a year. I have resigned, and
Benchao Li was duly elected by the PMC and approved unanimously by the
Board.
Please join me in congratulating Benchao!
Best
Stamatis Zampetakis created CALCITE-6162:
Summary: Add rule(s) to remove joins with constant single tuple
relations
Key: CALCITE-6162
URL: https://issues.apache.org/jira/browse/CALCITE-6162
Hey everyone,
The community is growing and more and more people get involved in
testing and voting for releases, which is great for the project. For
this purpose, I would like to send a brief reminder around the ASF
release policy [1] especially the part about approving releases. I
would
In our doc page we are already suggesting the use of the "newbie"
label [1]. If someone has cycles to go over JIRA issues and label them
accordingly that would be indeed very helpful for newcomers.
A few months ago, I did a quick cross project JIRA search for similar
labels and it appears that
I really appreciate the fact that many people jumped in and helped to
shoot this down and restabilise CI. Many thanks from my side as well
to everyone involved!
Best,
Stamatis
On Thu, Dec 7, 2023 at 12:46 AM Julian Hyde wrote:
>
> Thank you to everyone who worked on this - Stamatis, Benchao,
Upgraded Docker version to 24.0.7, build afdd53b and rerun the
built/test checks.
* Built from git tag and run tests OK
* Built from source artifacts and run tests OK
Changing my vote to +1 (binding)
Stamatis
On Thu, Dec 7, 2023 at 10:40 AM Stamatis Zampetakis wrote:
>
> Ubuntu 20.04
Ubuntu 20.04.6 LTS,
docker-compose version 1.25.5, build 8a1c60f6
Docker version 20.10.5, build 55c4c88
* Checked signatures and checksums OK
* Checked diff between repo and artifacts OK
* Went over release note OK
* Checked README.md (Logged CALCITE-6158)
* Checked LICENSE, NOTICE OK
* All
Stamatis Zampetakis created CALCITE-6160:
Summary: Missing ASF header from go.mod and go.sum files
Key: CALCITE-6160
URL: https://issues.apache.org/jira/browse/CALCITE-6160
Project: Calcite
Stamatis Zampetakis created CALCITE-6159:
Summary: SIGABRT when running tests with docker-compose
Key: CALCITE-6159
URL: https://issues.apache.org/jira/browse/CALCITE-6159
Project: Calcite
Stamatis Zampetakis created CALCITE-6158:
Summary: No instructions for building/testing the project in
README file
Key: CALCITE-6158
URL: https://issues.apache.org/jira/browse/CALCITE-6158
Ubuntu 20.04.6 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 8.1.1
* Checked signatures and checksums OK
* Checked diff between repo and artifacts OK
* Went over release note OK (Minor comments at the end)
* Checked README, NOTICE, LICENSE OK ([1, 2, 3, 4] should be ported to Avatica)
* All
Stamatis Zampetakis created CALCITE-6148:
Summary: Missing ASF header from some files in source distribution
Key: CALCITE-6148
URL: https://issues.apache.org/jira/browse/CALCITE-6148
Project
Thanks for driving this release Benchao! Well planned and timely executed.
Awesome work!
On Fri, Nov 10, 2023, 2:49 PM Benchao Li wrote:
> The Apache Calcite team is pleased to announce the release of Apache
> Calcite 1.36.0.
>
> Calcite is a dynamic data management framework. Its cost-based
>
Ubuntu 20.04.6 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 7.6.1
* Checked signatures and checksums OK
* Went over release note OK
* Checked diff between repo and artifacts OK
* Checked README, LICENSE, NOTICE files (Logged CALCITE-6095 to CALCITE-6099)
* Built from git tag and run tests
Stamatis Zampetakis created CALCITE-6099:
Summary: Missing LICENSE entry for _pygments.scss
Key: CALCITE-6099
URL: https://issues.apache.org/jira/browse/CALCITE-6099
Project: Calcite
Stamatis Zampetakis created CALCITE-6098:
Summary: Remove mentions of Jekyll from LICENSE and NOTICE files
Key: CALCITE-6098
URL: https://issues.apache.org/jira/browse/CALCITE-6098
Project
Stamatis Zampetakis created CALCITE-6097:
Summary: cobyism/gridism CSS dependency is mispelled in LICENSE
Key: CALCITE-6097
URL: https://issues.apache.org/jira/browse/CALCITE-6097
Project
Stamatis Zampetakis created CALCITE-6096:
Summary: Remove obsolete html5shiv and respond entries from LICENSE
Key: CALCITE-6096
URL: https://issues.apache.org/jira/browse/CALCITE-6096
Project
7a4a/core/src/main/java/org/apache/calcite/rex/RexLiteral.java#L214
> > > A comment from 2006 indicates that this field should not exist.
> > >
> > > Another example is https://github.com/apache/calcite/pull/3411, where I
> > > tried to fix up some problems with the
Upgrading dependencies is an important topic thanks for starting the
discussion Hongyu.
In terms of tooling, my experience with Dependabot in Apache Hive is
rather negative. Out of 52 PRs [1] raised by the bot 34 [2] are
failing the build/tests. In most cases committers do not follow-up to
Welcome Hongyu, and thanks a lot for the work you are doing for the project!
Best,
Stamatis
On Fri, Nov 3, 2023 at 3:57 AM Hongyu Guo wrote:
>
> Thank you for your introduction! I am delighted to join the Calcite
> community, and I am also grateful for your recognition of me.
>
> I have just
Congratulations Runkang, keep up the good work!
Best,
Stamatis
On Fri, Nov 3, 2023 at 3:57 AM Hongyu Guo wrote:
>
> Congratulations!
>
> Best,
> Hongyu Guo
>
> On Fri, Nov 3, 2023 at 10:16 AM Dan Zou wrote:
>
> > Congrats, Runkang!
> >
> > Best,
> > Dan Zou
> >
> >
> >
> >
> >
> > > 2023年11月3日
The only job that we have for publishing snapshots is on Jenkins [1].
The problem of missing nexus username/password credentials seems
similar to what we encountered in the past in INFRA-20044.
Best,
Stamatis
[1] https://ci-builds.apache.org/job/Calcite/job/Calcite-snapshots
[2]
Apache Calcite's Project Management Committee (PMC) has invited Lei Shen to
become a committer, and we are pleased to announce that they have accepted.
Lei has added many new optimizer rules to the project enhancing the
query plans for Calcite and downstream projects and pushed various
In some projects where I was involved and there was the notion of
"system fields" these used to be "special" columns on the table level
that could be used in queries but they were ignored when expanding the
"*".
Implementation wise, I think we introduced a new interface (not
necessarily connected
Apache Calcite's Project Management Committee (PMC) has invited Ran Tao to
become a committer, and we are pleased to announce that he has accepted.
Ran has implemented numerous improvements and fixes in the past few
months. He has added new SQL functions to the Spark library, addressed
various
Apache Calcite's Project Management Committee (PMC) has invited Mihai
Budiu to become a committer, and we are pleased to announce that he
has accepted.
Mihai has addressed numerous compile and runtime issues in SQL
functions and has made several significant improvements to the test
infrastructure
Great content Mihai, thanks for putting this together!
As Julian suggested the whole content of the blog could be put in a
news entry under the respective page [1].
Alternatively, if it is a link to an external site you could add it
under the external resources section [2].
Many apache projects
Hello community and happy birthday Calcite,
Eight years ago (22 October 2015) Calcite graduated as a top-level
Apache project [1]. At that point, the community decided to have an
annual “state of the project” discussion, and we arrived at that time
of the year.
We have had three Calcite releases
Stamatis Zampetakis created CALCITE-6053:
Summary: Upgrade Calcite to Avatica 1.24.0
Key: CALCITE-6053
URL: https://issues.apache.org/jira/browse/CALCITE-6053
Project: Calcite
Issue
Indeed the ideal would be to have some liberty around the supported
datetime formats and it would be great if we find people who want to
contribute in this direction.
However, this discussion is more about converging and taking a
decision around CALCITE-5678 and CALCITE-5957.
The results of the
Hello,
Below you can find a draft of this quarter's board report. I plan to
submit the final version next Monday (October 9, 2023).
Please let me know if you have any additions or corrections.
Best,
Stamatis
---
## Description:
Apache Calcite is a
Hey everyone,
CALCITE-5678, which landed recently in Avatica, enforces strict
validation of datetime literals and is inline with the SQL standard
specification. However, this strict validation also leads to behavior
changes (e.g., CALCITE-5957) since some previously "valid" dates are
now
Hey Ian,
I don't think there is such a rule in Calcite but you may find similar
ideas in rules present in other projects.
In Hive for instance, there is the HivePreFilteringRule [1, 2] that
pushes "redundantly" some filters below other operations in the tree.
What is inherently problematic with
Hello,
There are some pointers on DruidAdapterIT Javadoc [1]. If you have
problems setting up the environment let me know and I will try to
help.
Best,
Stamatis
[1]
Looks like a staleness (gradle caches, build dirs) issue. Clean
everything and start from scratch normally it should go away.
Best,
Stamatis
On Fri, Sep 22, 2023 at 9:43 AM Benchao Li wrote:
>
> I couldn't reproduce the problem you described locally.
>
> And looking at the history of the main
If we want to argue about if a type is valid or not I don't see a better
place other than the the type factory. I don't know what exactly is the
need here but if type checking should be performed in another place I would
be curious to know more about this use case.
On Tue, Aug 8, 2023, 6:19 PM
Hey Mihai,
I'm not sure to which part of calcite you refer to by saying that it
supports arbitrary precision strings but it is not uncommon for consumers
to use only a single component from calcite (say the parser) so I wouldn't
be surprised if there are implementation gaps in other places.
I would say that type checks for precision/scale etc would fit better
inside the RelDataTypeFactory and its respective type system.
Best,
Stamatis
On Mon, Aug 7, 2023 at 12:39 AM wrote:
>
> I found this documentation for Oracle DECIMAL data type:
>
Hey Mihai,
Indeed the .iq files are mostly end-to-end tests in Calcite. The
Quidem [1] framework is used for running these tests. The Quidem
approach is pretty neat cause we don't have to carry Java boilerplate
code and formatting around which makes the tests much easier to read,
write, inspect
Just to clarify that only CALCITE-5865 is a release blocker. All the
other things are just minor that can be fixed after the release.
On Thu, Jul 20, 2023 at 3:12 PM Xiong Duan wrote:
>
> Hello Calcite Community,
> I'm canceling this vote [VOTE] Release Apache Calcite 1.35.0
> (release
gt; 6. RM tallys votes and if the vote fails, builds the next RC, starting
> from step 1.
> 7. If the vote passes, RM tags a final release.
> 8. CI picks up the tag and automatically build and signs artifacts.
> 9. RM announces to the list and updates the website announcing the release.
>
>
Hello,
Allowing CI to automate part of the release process is now approved by
LEGAL and some projects are already taking advantage of it. For more
information check out the respective thread [1].
The Calcite release preparation is quite automated already so we may
not really need this at this
Ubuntu 20.04.6 LTS, jdk1.8.0_261, Gradle wrapper, Gradle 7.6.1
* Checked signatures and checksums OK
* Went over release note OK
* Checked README, LICENSE, NOTICE, and licenses directory (in source
distribution) OK
* Checked diff between git repo and release sources (diff -qr
calcite-git
Thanks for preparing the release Xiong Duan! Unfortunately, I get the
same problem with Ruben with regards to signature verification.
* Verified checksum: OK
* Verified signature: KO
gpg --verify apache-calcite-1.35.0-src.tar.gz.asc
gpg: assuming signed data in 'apache-calcite-1.35.0-src.tar.gz'
@Tanner No worries we all did this at some point in time, thanks a lot
for following up!
@Stanilovsky: I prefer keeping force push in place and avoiding messy
reverts that are usually necessary in various situations where we make
a mistake. All commits are archived so there is nothing that we
Hello,
It appears that there was a force push to main yesterday [1] rewriting
the history for a bunch of commits. I don't know if it was intentional
or not but it seems that now resolved JIRAs (after CALCITE-5810 I
think) are pointing to non-existent commits.
Can someone please update the JIRA
.
+---+-+
| committer | reviews |
+---+-+
| Julian Hyde | 28 |
| Benchao Li | 12 |
| rubenada | 8 |
| Jiajun | 8 |
| Stamatis Zampetakis | 3 |
| Tanner Clary <116591231+ta
Hello,
Below you can find a draft of this quarter's board report. I plan to
submit it next Tuesday (July 11, 2023).
Please let me know if you have any additions or corrections.
Best regards,
Stamatis
-
## Description:
Apache Calcite is a
Apache Calcite's Project Management Committee (PMC) has invited TJ Banghart to
become a committer, and we are pleased to announce that they have accepted.
TJ has been contributing to the community for about a year now. They
introduced many new SQL functions for parsing and formatting dates,
Apache Calcite's Project Management Committee (PMC) has invited Dan Zou to
become a committer, and we are pleased to announce that they have accepted.
Dan has been doing some great work for the project over the past few
months. They implemented and enabled multiple new SQL functions for
BigQuery
Apache Calcite's Project Management Committee (PMC) has invited Zhe Hu to
become a committer, and we are pleased to announce that they have accepted.
Zhe Hu has been contributing to the project for a while now. They
improved the stability of the ElasticSearch adapter, worked on
supporting new
Apache Calcite's Project Management Committee (PMC) has invited Jacky Lau to
become a committer, and we are pleased to announce that they have accepted.
Jacky has started contributing to the project very recently and in a
very short time they landed many notable improvements around ARRAY and
MAP
22-06-17 [E] [expires: 2038-06-13]
> >
> > --
> > Michael Mior
> > mm...@apache.org
> >
> >
> > On Mon, Jun 26, 2023 at 3:27 AM Stamatis Zampetakis
> > wrote:
> >
> > > Hello,
> > >
> > > The last virtual key signing pa
public
keys' fingerprint (gpg --fingerprint) before the meeting.
pub rsa4096 2019-03-15 [SC] [expires: 2027-03-15]
0474 9577 FD93 4674 B9CD 45C5 D77C 3383 F192 7570
uid [ultimate] Stamatis Zampetakis
uid [ultimate] Stamatis Zampetakis
sub rsa4096 2019-03-15 [E
I had a quick look at the OSS-Fuzz project [1] and I get the
impression that it is not only security oriented but a general
framework for fuzzy testing components.
I am sure that fuzzy testing can uncover many bugs (especially small
ones) so it's worth having I guess. However, receiving
Hello,
We definitely welcome contributions that could improve the graph query
capabilities in Calcite. If something is part of the SQL standard then
it can be contributed to the core SQL parser of Calcite. If it is not
standard but still widely accepted/used it should probably land in the
babel
Apache Calcite's Project Management Committee (PMC) has invited Oliver
Lee to become a committer, and we are pleased to announce that they
have accepted.
Oliver started working with us around November 2022 and since then
they contributed multiple SQL functions to the Calcite repository
bringing
Stamatis Zampetakis created CALCITE-5773:
Summary: Gradle show tasks fails when creating
javadocAggregateIncludingTests
Key: CALCITE-5773
URL: https://issues.apache.org/jira/browse/CALCITE-5773
Apache Calcite's Project Management Committee (PMC) has invited Tanner
Clary to become a committer, and we are pleased to announce that they
have accepted.
In less than 5 months, Tanner has introduced, enabled, and tested over
30 SQL functions in Calcite. They have been a driving force in
Hey Vladislav,
I see two operators relevant to your use-case:
* Spool [1]
* Correlate [2]
Both allow some form of propagating data from one side of the join to
the other. Check the code and relevant discussions to see how they are
used.
Best,
Stamatis
[1]
There is also the EnumerableBatchNestedLoopJoin [1] algorithm which
can batch multiple values into one request. There are also some past
discussions in the list around this concept (for instance [2]).
Best,
Stamatis
[1]
Stamatis Zampetakis created CALCITE-5705:
Summary: Generalize RemoveEmptySingleRule to work with arbitrary
relations and pruning configurations
Key: CALCITE-5705
URL: https://issues.apache.org/jira/browse
if you have any questions or suggestions on this approach.
> >
> > Thanks,
> > Hanu
> >
> >
> >
> >
> > On Wed, Apr 19, 2023 at 11:15 AM Julian Hyde
> > wrote:
> >
> >> Thank you, Stamatis. This is helpful. I have linked to this emai
Following up on the authorization part lots of things can be achieved
through the use of views. Views can be used to restrict the columns
and rows that are visible to certain users and it is a common way of
handling permissions.
Here also two other JIRA tickets with discussion around this topic:
The topic is really interesting, thanks for sharing your ideas Zoltan!
I see no drawbacks adding the new transformation rule; definitely worth
having! However, adding them to the default rule set or using them in a
cost based decision may require much more work/thinking.
Calcite's built-in cost
Stamatis Zampetakis created CALCITE-5675:
Summary: Infer predicates for anti-join
Key: CALCITE-5675
URL: https://issues.apache.org/jira/browse/CALCITE-5675
Project: Calcite
Issue
Stamatis Zampetakis created CALCITE-5669:
Summary: Remove trivial correlates from the query plan
Key: CALCITE-5669
URL: https://issues.apache.org/jira/browse/CALCITE-5669
Project: Calcite
PR comments. But that
> > won't be a big problem for me.
> >
> > Michael Mior 于2023年4月19日周三 18:43写道：
> >
> >> +1 from me as well
> >>
> >> On Wed, Apr 19, 2023, 04:19 Stamatis Zampetakis wrote:
> >>
> >>> Hello,
>
Hello,
Everything that happens in a GitHub PR creates a worklog entry under
the respective JIRA ticket.
For every worklog entry we receive a notification from j...@apache.org
when we are watching an issue. The worklog entry and email
notification usually appear messy.
Moreover, if we are
Hey Mihai,
Thanks for starting this discussion!
Let's focus on the first question for now:
Q1: Should the new slt module under PR-3145 [1] become part of Calcite
repo or get its own?
For those who have not followed the discussion under the CALCITE-5615
[2] let me try to summarize a few things
Few quick thoughts about this.
For to the problem of query minimization/redundant joins the simpler
scenarios that I can think of are the following:
# Scenario A
select e1.id from emp e1 inner join emp e2 on e1.name = e2.name;
If you know the name column is UNIQUE then you can drop the join on
For a long time this has been one of the main issues of the project
and I am happy to see discussions to address this issue.
I would like to mention that as a contributor, I am, and always have
been very grateful to people reviewing my work.
The fact that I became a committer of this project is
|
| Benchao Li | 9 |
| Stamatis Zampetakis | 4 |
+---+-+
The number of non-commiter commits has almost doubled in the last quarter
which is a good thing. Unfortunately the number of active reviewers is
still pretty
It's true that I've never seen a fake PR so far in the ASF repos but
at the same time I am not following every single PR.
I can understand the approval for first time contributors but keeping
the approval for everyone seems a bit too much.
Best,
Stamatis
On Wed, Mar 29, 2023 at 5:04 AM 王鹏
Hi LakeShen,
The last discussion about this topic was back in 2021 [1].
Apart from cleanup there is nothing major to be done as part of 2.0 so
there is no big rush to get it out.
Best,
Stamatis
[1] https://lists.apache.org/thread/p6svy4hps193g4knhsksv7psx0osgvq7
On Wed, Mar 29, 2023 at 8:51
Hey Ian,
I think you are referring to the problem of query minimization and at
the moment we don't have any such rules in Calcite but it would be a
valuable contribution.
Apart from the algorithm itself, it might be necessary to introduce
some new metadata provider for PK-FK relationships
hem
>
> On Tue, Mar 21, 2023 at 10:32 AM Benchao Li wrote:
>
> > As I've said in another ML thread[1], I will volunteer to do one.
> >
> > [1] https://lists.apache.org/thread/dcf6o3mdzflh7brsklgoy7fd1njy8jjz
> >
> > Stamatis Zampetakis 于2023年3月21日周二 17:01写道：
Hi everyone,
In the last year or so we had the following people helping out with
releasing Calcite.
1.30.0 Liya Fan
1.31.0 Adrei Sereda
1.32.0 Julian Hyde
1.33.0 Jess Balint
1.34.0 Stamatis Zampetakis
Big thanks to everyone!
Now we should see who can help out with the next releases.
@Duan
All the slides and videos from the meetup are now online. The links
for the talks can be found on the website [1].
Best,
Stamatis
[1] https://calcite.apache.org/community/#talks
On Thu, Mar 16, 2023 at 11:28 AM Stamatis Zampetakis wrote:
>
> I would like to thank everyone who at
1 - 100 of 1025 matches
Mail list logo
