FYI, it’s not reproduced with Calcite 1.35
> On 7 Nov 2023, at 03:10, Julian Hyde wrote:
>
> Did you find an existing Jira case? If not, could you log one? You should
> create a minimal test case and figure out what are the essential features
> that are necessary to reproduce this problem. Ide
Hi, Egor, I agree with Julian's opinion, maybe you can use calcite's test
set for this case, such as emp, dept, hr and other schema/tables.
then developers will easily locate the problem.
Some bugs may have persisted in earlier versions to this day, some were
later fixed, and some were covered up.
I wonder which *Test.java should I try to use as a template? I need smth that
parses the SQL and uses Volcano optimizer as the stacktrace shows it fails
during optimization.
BTW, it happened during Apache Druid query execution and I saw the Druid custom
join rule was engaged so I thought initi
Dmitry Sysolyatin created CALCITE-6100:
--
Summary: The equalsDeep of SqlRowTypeNameSpec returns wrong result
Key: CALCITE-6100
URL: https://issues.apache.org/jira/browse/CALCITE-6100
Project: Calci
Dmitry Sysolyatin created CALCITE-6101:
--
Summary: SqlCollectionTypeNameSpec should preserve the nullability
property of the element type
Key: CALCITE-6101
URL: https://issues.apache.org/jira/browse/CALCITE-61
If the issue can be reproduced using a SQL query on a standard data set, the
best test case is often a Quidem fragment.
A recent commit that did that:
https://github.com/apache/calcite/commit/1245db6201. They also added a test to
the applicable unit test.
I confess it’s not very easy to run Qu
Thank you, TJ and Gavin.
Appreciate you taking the time to provide such helpful suggestions.
I will try these out and revert, in case I face any more issues.
Best Regards,
Raja Senapati
On 2023/11/08 18:53:54 TJ Banghart wrote:
> Hello Raja and welcome to Calcite!
>
> I have found it helpful to t
