Jin>Some of my users write tests based on functionalities provided from
Calcite
Jin>test framework
Frankly speaking, it was somewhat surprising for me, and it does bring
extra demand for having a proper calcite-test-framework.
The naming is hard, however, I would suggest
artifactId=calcite-test-f
Hi Guys,
I want to contribute to Apache Calcite.
Would you please give me the permission as a contributor?
My JIRA ID is yimeisun.
I've added you as a contributor. Thanks!
--
Michael Mior
mm...@apache.org
Le mer. 25 déc. 2019 à 06:59, SUN RUN a écrit :
>
> Hi Guys,
>
> I want to contribute to Apache Calcite.
> Would you please give me the permission as a contributor?
> My JIRA ID is yimeisun.
Shuo Cheng created CALCITE-3631:
---
Summary: Support SQL hints for Calc
Key: CALCITE-3631
URL: https://issues.apache.org/jira/browse/CALCITE-3631
Project: Calcite
Issue Type: Sub-task
xzh_dz created CALCITE-3632:
---
Summary: Add IntersectToIntersectUnifyRule in SubstitutionVisitor
Key: CALCITE-3632
URL: https://issues.apache.org/jira/browse/CALCITE-3632
Project: Calcite
Issue Type
Personally, I would opt for a more permissive build.
Unexpected line endings is kind of subjective.
I guess there are people who use Windows and they still have their editors
configured to use LF endings.
Moreover, checking other opensource projects it is kind of rare to release
source code in mu