[jira] [Created] (CALCITE-6365) Support for RETURNING clause of JSON_QUERY

Dawid Wysakowicz created CALCITE-6365: - Summary: Support for RETURNING clause of JSON_QUERY Key: CALCITE-6365 URL: https://issues.apache.org/jira/browse/CALCITE-6365 Project: Calcite

[jira] [Created] (CALCITE-6342) Use highest input precision for datetime with/without local time zone

Dawid Wysakowicz created CALCITE-6342: - Summary: Use highest input precision for datetime with/without local time zone Key: CALCITE-6342 URL: https://issues.apache.org/jira/browse/CALCITE-6342

[jira] [Created] (CALCITE-4390) SqlMatchRecognize returns wrong operand list

Dawid Wysakowicz created CALCITE-4390: - Summary: SqlMatchRecognize returns wrong operand list Key: CALCITE-4390 URL: https://issues.apache.org/jira/browse/CALCITE-4390 Project: Calcite

[jira] [Created] (CALCITE-4085) Improve nullability support for fields of structured type

Dawid Wysakowicz created CALCITE-4085: - Summary: Improve nullability support for fields of structured type Key: CALCITE-4085 URL: https://issues.apache.org/jira/browse/CALCITE-4085 Project

Re: Nullability support in structured types

rnType) > - AliasNamespace#validateImpl > > At first glance, I think those changes are fair, and could be integrated as > a contribution. As I see it, you are applying in different methods the > logic that was already in place for SqlDotOperator#inferReturnType. > > Best regar

Nullability support in structured types

Hi devs, I wanted to reach out to the Apache Calcite community about an issue with nullability of structured types we observed in Apache Flink. First of all let me give you a quick introduction why it is important for us. What we want to support eventually is that we want to be able to map POJOs

[jira] [Created] (CALCITE-2747) No exception when ambigous column reference defined in PARTITION BY and MEASURES clause

Dawid Wysakowicz created CALCITE-2747: - Summary: No exception when ambigous column reference defined in PARTITION BY and MEASURES clause Key: CALCITE-2747 URL: https://issues.apache.org/jira/browse/CALCITE

[jira] [Created] (CALCITE-2746) Cryptic exception when expression used in PARTITION BY clause in MATCH_RECOGNIZE

Dawid Wysakowicz created CALCITE-2746: - Summary: Cryptic exception when expression used in PARTITION BY clause in MATCH_RECOGNIZE Key: CALCITE-2746 URL: https://issues.apache.org/jira/browse/CALCITE-2746

Re: Problems about subsets clause order for MATCH_RECOGNIZE

 Let  me take an example:   SUBSET X=(A,B) > > >    I’m not very sure about the implementations of Oracle, but I’m > curious that why we use sortedSet to store the elements(A,B) of SUBSET > if we don’t need the “sorted”. > > > Best, > > Jiayi Liao > > >  Original

Re: Problems about subsets clause order for MATCH_RECOGNIZE

Hi Jiayi, I don't think it should any difference what is the order in the SUBSET clause. The PATTERN clause specifies the definitive order of pattern variables. SUBSET clause just groups them as a single entity you can reference. Therefore LAST/FIRST/PREV/NEXT/AFTER MATCH etc. will take into accou

[jira] [Created] (CALCITE-2708) UDAGs are not verified for single pattern variable in MATCH_RECOGNIZE

Dawid Wysakowicz created CALCITE-2708: - Summary: UDAGs are not verified for single pattern variable in MATCH_RECOGNIZE Key: CALCITE-2708 URL: https://issues.apache.org/jira/browse/CALCITE-2708

[jira] [Created] (CALCITE-2707) Information about distinct aggregation is lost in MATCH_RECOGNIZE

Dawid Wysakowicz created CALCITE-2707: - Summary: Information about distinct aggregation is lost in MATCH_RECOGNIZE Key: CALCITE-2707 URL: https://issues.apache.org/jira/browse/CALCITE-2707

[jira] [Created] (CALCITE-2664) Change default option for AFTER MATCH SKIP to SQL standard compliant one

Dawid Wysakowicz created CALCITE-2664: - Summary: Change default option for AFTER MATCH SKIP to SQL standard compliant one Key: CALCITE-2664 URL: https://issues.apache.org/jira/browse/CALCITE-2664