Hi Louis,
It's true that we have neglected a bit curating the JIRA tasks for newbies.
My suggestion would be to have a look in recently created bugs with no
assignee that lead to an exception [1] and pick one that you understand the
most.
Usually it is easier to get started if there is a test cas
Hello,
I don't want the current situation to be disheartening for anybody,
especially those who spend significant time on these code changes (Julian,
Vladimir).
Our common goal is to release 1.27.0 in the best possible conditions so
let's try to agree on the plan to move forward.
To do this, I thi
Stamatis,
Il Lun 16 Nov 2020, 10:20 Stamatis Zampetakis ha
scritto:
> Hello,
>
> I don't want the current situation to be disheartening for anybody,
> especially those who spend significant time on these code changes (Julian,
> Vladimir).
> Our common goal is to release 1.27.0 in the best possib
Stamatis>@Vladimir: Can you specify which JIRA issue(s) you would like to
see solved
Stamatis>for the next release?
RexProgramFuzzyTest should be enabled, and Sarg-related fuzzing should be
implemented as well.
RexFuzzer should generate Sarg expressions.
RexInterpreter should be able to evaluate s
And yet more passive-aggressive bulls**t from Vladimir:
https://github.com/apache/calcite/commit/c6b3fb7ddbf8aed981ff3fb0632c77216dbe68d6
I've force-pushed to remove it.
I plan to respond to Stamatis' thoughtful email later today. Also, I
think I may have a test case that demonstrates the issues
Alternatively, for the trait push down optimization effort, there are some
well defined tasks: https://issues.apache.org/jira/browse/CALCITE-4052. If
you are interested, you can pick up some tasks from there :) I am happy to
help you get familiar with those tasks and review your code.
-Rui
On
We currently maintain a release cadence of a new release every two
months. This puts the next release pretty close to Christmas next month.
Would it make sense if we push 1.27.0 back a few weeks until maybe after
new year? In the mean time, perhaps we can focus on getting these issues
fixed an
Pushing release 1.27 back to the New Year makes sense.
We need to do some work on Sargs. As to what that work should be,
things are going to get controversial. (I would appreciate help from
impartial elders like Stamatis, Francis, Haisheng to guide this
discussion to where we can agree.)
I agree
Julian>And I would love a SQL test case that shows that SEARCH is broken. :)
I give you 100 char SQL reproducer and you restore pull/2250.
Deal?
Julian>But it is good news for people using Calcite 1.26 - it is very
Julian>unlikely that they are being affected by the bug.
Calcite 1.26 is affected
Thanks everyone for the suggestions!
I will take a look at the suggested tasks and reach out if I have any
questions :)
Thanks again!
Best,
Louis
On Mon, Nov 16, 2020 at 2:16 PM Rui Wang wrote:
> Alternatively, for the trait push down optimization effort, there are some
> well defined tasks:
10 matches
Mail list logo