[jira] [Created] (CALCITE-3129) Automate website builds
Francis Chuang created CALCITE-3129: --- Summary: Automate website builds Key: CALCITE-3129 URL: https://issues.apache.org/jira/browse/CALCITE-3129 Project: Calcite Issue Type: Task Components: avatica, avatica-go, site Reporter: Francis Chuang Assignee: Francis Chuang -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-2871) Implement JSON_TABLE table function
[
https://issues.apache.org/jira/browse/CALCITE-2871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864601#comment-16864601
]
Forward Xu commented on CALCITE-2871:
-
hi [~zhztheplayer] [~julianhyde] I think the mysql jsontable syntax
implementation is also very good, the following is the relevant link.
[jsontable|[https://dev.mysql.com/doc/refman/8.0/en/json-table-functions.html]]
> Implement JSON_TABLE table function
> ---
>
> Key: CALCITE-2871
> URL: https://issues.apache.org/jira/browse/CALCITE-2871
> Project: Calcite
> Issue Type: Sub-task
>Reporter: Hongze Zhang
>Priority: Major
>
> Below is the syntax of JSON_TABLE described by ISO/IEC TR 19075-5[1]:
> {code}
> ::=
> JSON_TABLE
>
>
>[ ]
>[ ON ERROR ]
>
>
> ::=
> COLUMNS
>
> [ { }... ]
>
>
> ::=
>
> |
> |
> |
> ::=
>FOR ORDINALITY
>
> ::=
>
>[ PATH ]
>[ ON EMPTY ]
>[ ON ERROR ]
>
> ::=
> ERROR
> | NULL
> | DEFAULT
>
> ::=
> ERROR
> | NULL
> | DEFAULT
>
> ::=
>
> ::=
>
> FORMAT
> [ PATH ]
> [ WRAPPER ]
> [ QUOTES
> [ ON SCALAR STRING ] ]
> [ ON EMPTY ]
> [ ON ERROR ]
> ::=
> WITHOUT [ ARRAY ]
> | WITH [ CONDITIONAL | UNCONDITIONAL ] [ ARRAY ]
>
> ::=
> KEEP
> | OMIT
>
> ::=
> ERROR
> | NULL
> | EMPTY ARRAY
> | EMPTY OBJECT
>
> ::=
> ERROR
> | NULL
> | EMPTY ARRAY
> | EMPTY OBJECT
> ::=
> ERROR
> | EMPTY
> ::=
> NESTED [ PATH ]
> [ AS ]
>
> ::=
>
> ::=
>
> ::=
>
>
> ::=
>
> |
> ::=
> PLAN
> ::=
>
> |
> |
> ::=
>
> |
>
> ::=
>OUTER
>
> ::=
>INNER
>
> ::=
>
> |
>
> ::=
>UNION
> [ { UNION }... ]
> ::=
>CROSS
> [ { CROSS }... ]
>
> ::=
>
> |
>
> ::=
> PLAN DEFAULTparen>
> ::=
>
> [ ]
> |
> [ ]
>
> ::=
> INNER
> | OUTER
>
> ::=
> UNION
> | CROSS
> {code}
> A usage example:
> {code:sql}
> SELECT bookclub.id, jt.name, jt.type, jt.number
> FROM bookclub,
> JSON_TABLE ( bookclub.jcol, 'lax $'
> COLUMNS ( name VARCHAR(30) PATH 'lax $.Name',
>NESTED PATH 'lax $.phoneNumber[*]'
>COLUMNS ( type VARCHAR(10) PATH 'lax $.type',
>number CHAR(12) PATH 'lax
> $.number' )
> ) AS jt;
> {code}
> As another reference, Oracle has a non-standard implementation[2] of this
> function.
> [1]
> http://standards.iso.org/ittf/PubliclyAvailableStandards/c065143_ISO_IEC_TR_19075-5_2016.zip
> [2] https://docs.oracle.com/database/121/SQLRF/functions092.htm#SQLRF56973
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CALCITE-3127) Support ALTER VIEW Statement
[
https://issues.apache.org/jira/browse/CALCITE-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864583#comment-16864583
]
pingle wang commented on CALCITE-3127:
--
If alter view syntax not worth doing, I will not develop this feature, thanks.
> Support ALTER VIEW Statement
>
>
> Key: CALCITE-3127
> URL: https://issues.apache.org/jira/browse/CALCITE-3127
> Project: Calcite
> Issue Type: Improvement
> Components: server
>Affects Versions: 1.19.0
>Reporter: pingle wang
>Priority: Major
> Labels: pull-request-available
> Fix For: next
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> support alter view statement :
> {code:java}
> ALTER VIEW name
> [ '(' columnName [, columnName ]* ')' ]
> AS query
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CALCITE-3127) Support ALTER VIEW Statement
[
https://issues.apache.org/jira/browse/CALCITE-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864324#comment-16864324
]
Julian Hyde commented on CALCITE-3127:
--
Yes, except that we don't support any of those options today. So the syntax
would be trivial: {{ALTER VIEW;}}. Not worth doing.
> Support ALTER VIEW Statement
>
>
> Key: CALCITE-3127
> URL: https://issues.apache.org/jira/browse/CALCITE-3127
> Project: Calcite
> Issue Type: Improvement
> Components: server
>Affects Versions: 1.19.0
>Reporter: pingle wang
>Priority: Major
> Labels: pull-request-available
> Fix For: next
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> support alter view statement :
> {code:java}
> ALTER VIEW name
> [ '(' columnName [, columnName ]* ')' ]
> AS query
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (CALCITE-3128) Joining two tables producing only NULLs will return 0 rows
[
https://issues.apache.org/jira/browse/CALCITE-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16864265#comment-16864265
]
Muhammad Gelbana commented on CALCITE-3128:
---
My analysis so far is that {{leftKeys}} and {{rightKeys}} for
EnumerableHashJoin (Recently named EnumerableJoin) are blank, which illudes
{{PhysTypeImpl.generateAccessor(List)}} to return an expression of an
empty list.
{{leftKeys}} and {{rightKeys}} are blank because while constructing a Join
node, {{JoinInfo.of(RelNode, RelNode, RexNode)}} uses
{{RelOptUtil.splitJoinCondition(RelNode, RelNode, RexNode, List,
List, List)}} to fill up {{leftKeys}} and {{rightKeys}} but
it doesn't because the condition is always true (i.e cartesian product).
I'm still not sure where or how to fix this.
> Joining two tables producing only NULLs will return 0 rows
> --
>
> Key: CALCITE-3128
> URL: https://issues.apache.org/jira/browse/CALCITE-3128
> Project: Calcite
> Issue Type: Bug
> Components: core
>Affects Versions: 1.20.0
>Reporter: Muhammad Gelbana
>Priority: Major
>
> The following queries will return 0 rows while they're expected to ruturn
> rows with NULLs in them.
> {code:sql}
> SELECT *
> FROM (SELECT NULLIF(5, 5)) a, (SELECT NULLIF(5, 5)) b
> {code}
> {code:sql}
> SELECT *
> FROM (VALUES (NULLIF(5, 5)), (NULLIF(5, 5))) a, (VALUES (NULLIF(5, 5)),
> (NULLIF(5, 5))) b
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (CALCITE-3128) Joining two tables producing only NULLs will return 0 rows
Muhammad Gelbana created CALCITE-3128:
-
Summary: Joining two tables producing only NULLs will return 0 rows
Key: CALCITE-3128
URL: https://issues.apache.org/jira/browse/CALCITE-3128
Project: Calcite
Issue Type: Bug
Components: core
Affects Versions: 1.20.0
Reporter: Muhammad Gelbana
The following queries will return 0 rows while they're expected to ruturn rows
with NULLs in them.
{code:sql}
SELECT *
FROM (SELECT NULLIF(5, 5)) a, (SELECT NULLIF(5, 5)) b
{code}
{code:sql}
SELECT *
FROM (VALUES (NULLIF(5, 5)), (NULLIF(5, 5))) a, (VALUES (NULLIF(5, 5)),
(NULLIF(5, 5))) b
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (CALCITE-3112) Support Window in RelToSqlConverter
[ https://issues.apache.org/jira/browse/CALCITE-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-3112: Labels: pull-request-available (was: ) > Support Window in RelToSqlConverter > --- > > Key: CALCITE-3112 > URL: https://issues.apache.org/jira/browse/CALCITE-3112 > Project: Calcite > Issue Type: Improvement > Components: core >Affects Versions: 1.19.0 >Reporter: Feng Zhu >Assignee: TANG Wen-hui >Priority: Major > Labels: pull-request-available > > Current now, RelToSqlConverter does not support Window, due to its original > design for RelNode of JDBC-type. > When we try to convert EnumerableWindow node back to SQL, it will fail. > For more general use, I think we need to implement this feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
