Hi Haisheng,
I am interested in volunteering.
Best,
Liya Fan
On Fri, Jun 4, 2021 at 6:50 AM Julian Hyde wrote:
> Yes, I am release manager for 1.28. I’ll aim to release first week of
> August.
>
> Somewhat related to the call for release managers: we need active
> committers. (Stamatis, can
Yes, I am release manager for 1.28. I’ll aim to release first week of August.
Somewhat related to the call for release managers: we need active committers.
(Stamatis, can you run your stats on PRs and active committers?) On May 21, I
noted that PR backlog is building up, and appealed for 5
Hi all,
In the next half year, I hope we can get back to the pace of release for every
2 months. We need more release managers for the next few releases, is there any
one interested in volunteering to be release manager?
Currently Julian is the release manager for 1.28.0, we need 3 more for
Hi all,
Apache Calcite 1.27.0 has been released, therefore the master is again open.
Best,
Stamatis
Thanks to everyone who has tested the release candidate and given
their comments and votes.
The tally is as follows.
5 binding +1s:
Stamatis Zampetakis
Francis Chuang
Julian Hyde
Haisheng Yuan
Ruben Quesada Lopez
1 binding -1:
Vladimir Sitnikov
2 non-binding +1s:
Alessandro Solimando
Igor
Rafay A created CALCITE-4636:
Summary: Wrong RelCollation if Group by field appears in Order by
clause
Key: CALCITE-4636
URL: https://issues.apache.org/jira/browse/CALCITE-4636
Project: Calcite
James Kim created CALCITE-4635:
--
Summary: Distinct on aggregate window functions produce wrong
result
Key: CALCITE-4635
URL: https://issues.apache.org/jira/browse/CALCITE-4635
Project: Calcite
Yingyu created CALCITE-4634:
---
Summary: Improve AggregateProjectPullUpConstantsRule to remove all
constant keys
Key: CALCITE-4634
URL: https://issues.apache.org/jira/browse/CALCITE-4634
Project: Calcite
The PR needs to fix a bug or implement a feature. So, first you should
log a JIRA case describing what doesn’t work. Write tests for what
doesn’t work that you want to make work. (Or maybe you can
refactor/generalize existing tests.) Then submit a PR, and we will
review that PR on the
The PR needs to fix a bug or implement a feature. So, first you should log a
JIRA case describing what doesn’t work. Write tests for what doesn’t work that
you want to make work. (Or maybe you can refactor/generalize existing tests.)
Then submit a PR, and we will review that PR on the basis of
Julian, thanks for reply and comments.
Can you explain, is it would possible to commit PR containing
deduplication code moved upper this flag ?
If so - i will create PR and rerun all existing tests, of course.
Thanks !
Master is a moving target. Apparently you are using a version of the
code
Ruben,
The next time the case reproduces, please collect the core dump.
At least you would be able to analyze it later.
It might be a VM issue (e.g. failing compilation), or it might be a
concurrency issue (e.g. data race in the parser code),
or something completely different.
You might find
Hello,
in a downstream project we have experienced a strange phenomenon around
Calcite SQL parser.
To sum up, while running (sequentially) several thousand times (around 20K)
different instances of the "same" query (not sure if the query itself is
relevant, but just in case I share how it looks
13 matches
Mail list logo