Please also subscribe to the dev list.
Julian
> On Sep 5, 2022, at 21:19, Francis Chuang wrote:
>
> Welcome to Calcite!
>
> I've added you as a contributor in jira.
>
> Francis
>
>> On 6/09/2022 2:17 pm, 朱文状 wrote:
>> Hi,
>> I want to contribute to Apache Calcite. Would you please give me
Welcome to Calcite!
I've added you as a contributor in jira.
Francis
On 6/09/2022 2:17 pm, 朱文状 wrote:
Hi,
I want to contribute to Apache Calcite. Would you please give me the
contributor permission?
My JIRA Username is wenzhuang.zwz .
Best,
Wenzhuang Zhu.
Hi,
I want to contribute to Apache Calcite. Would you please give me the
contributor permission?
My JIRA Username is wenzhuang.zwz .
Best,
Wenzhuang Zhu.
Wenzhuang Zhu created CALCITE-5267:
--
Summary: Remove useless variable 'newCasts' in
AggregateCaseToFilterRule
Key: CALCITE-5267
URL: https://issues.apache.org/jira/browse/CALCITE-5267
Project:
Hi, all:
I want to know which virtual column is in use. For example,
```
CREATE TABLE peoples(age int, virtual_age int as (age + 1) virtual);
SELECT virtual_age from peoples;
```
After converting, the virtual column is expanded to expression.
```
LogicalProject(virtual_age=[+($0, 1)])
I don't know the whole history behind this but I can think of the following
reasons:
* (Legacy) Instant class, et al., came with JDK 8 and Calcite code is much
older than that
* (Performance) Operations between longs are much more efficient than the
respective ones with objects
* (Code reuse) Code
I have created task - https://issues.apache.org/jira/browse/CALCITE-5266
On Sat, Sep 3, 2022 at 5:22 PM Dmitry Sysolyatin
wrote:
> Ok, I will create a task.
> Was there any reason why Long was chosen initially for representing
> TIMESTAMP instead of using java.time.Instant ?
> I propose to use
Dmitry Sysolyatin created CALCITE-5266:
--
Summary: Increase precision of TIMESTAMP, INTERVAL types to
microseconds, nanoseconds
Key: CALCITE-5266
URL: https://issues.apache.org/jira/browse/CALCITE-5266
