I agree with Julian, we should get the 1.27.0 out as soon as possible.
I can try to prepare RC0 between the 28 and 30 of May, if people agree on
this.
Alternatively, I will have a bit more time around 17 to 20 of June.
I will try to get 2-3 PRs in before starting the RC.
Best,
Stamatis
On Fri,
Vladimir Sitnikov created CALCITE-4618:
--
Summary: Refine dependency declarations to better account for type
annotations
Key: CALCITE-4618
URL: https://issues.apache.org/jira/browse/CALCITE-4618
P
Now Avatica 1.18 has been released (thanks, Francis!) we should press on with
Calcite 1.27.
Who is release manager? Stamatis, You volunteered to be release manager for
1.27 [1] but I would be happy to jump in. Let me know.
There is a backlog of PRs that look good enough to go into 1.27. How to
One principle we should apply here: if a so-called “hint” causes the physical
operator to have a different cost then it’s not a hint; it is a parameter. An
example would be the buffer size allocated to an external sort. You might
conceivably have two instances of that operator with different buf
Sylvain Crozon created CALCITE-4617:
---
Summary: Wrong offset when SortJoinTransposeRule pushes a sort
node with an offset
Key: CALCITE-4617
URL: https://issues.apache.org/jira/browse/CALCITE-4617
Pro
Can you add your proposed fix to the bug, and we can discuss there.
> On May 21, 2021, at 2:33 AM, Vladimir Ozerov wrote:
>
> Hi,
>
> I created two issues for two distinct bugs in AggregateUnionTransposeRule:
>
> 1. https://issues.apache.org/jira/browse/CALCITE-4616 - the problem with
> a
Hi,
I created two issues for two distinct bugs in AggregateUnionTransposeRule:
1. https://issues.apache.org/jira/browse/CALCITE-4616 - the problem with
a partial Aggregate push-down
2. https://issues.apache.org/jira/browse/CALCITE-4615 - the problem with
an incorrect type of aggregate
Vladimir Ozerov created CALCITE-4616:
Summary: AggregateUnionTransposeRule causes row type mismatch when
some inputs have unique grouping key
Key: CALCITE-4616
URL: https://issues.apache.org/jira/browse/CALCIT
Vladimir Ozerov created CALCITE-4615:
Summary: AggregateUnionTransposeRule may assign wrong aggregate
function to input
Key: CALCITE-4615
URL: https://issues.apache.org/jira/browse/CALCITE-4615
Pr
There are use cases where it makes sense to keep/pass hints and others that
I assume makes sense to discard them (not used by the operator, rules,
implementors, etc).
Since the discussion was brought up for the Enumerable operators what's the
benefit of retaining hints at this level?
As far as I r
10 matches
Mail list logo
