+1 too for bringing up this discussion, navigating through related issues
is very important.
Benchao: in general the most important is to put the link (even just
"relates to" or "duplicates" as Julian said), we can defer more complex
relationships to the description or comments.
Other ones I use
Thanks Stamatis for the reminder. I'm also +1 for it.
I agree that bi-directional links is helpful and important. But in which
kind of cases should we use it and to use what kind of the link sometimes
is not that clear.
Julian's reply answers second question, and it is great to not worry about
I’ll review a couple of PRs if two or three people volunteer to review a couple.
Julian
> On Oct 13, 2022, at 2:45 PM, Francis Chuang wrote:
>
> Hey everyone,
>
> There are currently 13 open pull requests for Avatica[1]. Since we're not in
> the middle of a Calcite release, would it be
I’d be surprised if a query of that shape is sufficient to reproduce the case.
So the problem is with your schema. But your “schema” doesn’t look like
something that would fit into a Calcite JSON model file.
If you can come up with a reproducible test case, you should log a jira case.
> On
+1
Thanks for this reminder, Stamatis. Bi-directional links help us navigate
around the graph of related issues, identify duplicate bugs, do forensics, and
also to break down the roadmap (aspirational features) into smaller,
incremental tasks. I use them a lot.
Our Jira instance is an amazing
Hello Thomas,
Thank you for your answer.
I already register the hint strategies as in KuduQuery.java#L88. However, no
hints are visible until I surround the JDBC call with a
SqlToRelConverter hook, just like in my first email.
I looked at Kudu's test suite and discovered that kudu also
Hi all,
This is a small tip/reminder for everyone using JIRA.
It is very common and convenient to refer to other tickets by adding the
CALCITE-X pattern in summary, description, and comments.
The pattern allows someone to navigate quickly to an older JIRA from the
current one but not the
