[jira] [Assigned] (CALCITE-1440) Implement planner for converting multiple SQL statements to unified RelNode Tree
[
https://issues.apache.org/jira/browse/CALCITE-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
TJ Banghart reassigned CALCITE-1440:
Assignee: TJ Banghart
> Implement planner for converting multiple SQL statements to unified RelNode
> Tree
>
>
> Key: CALCITE-1440
> URL: https://issues.apache.org/jira/browse/CALCITE-1440
> Project: Calcite
> Issue Type: New Feature
>Reporter: Chinmay Kolhatkar
>Assignee: TJ Banghart
>Priority: Major
>
> This can be implemented as a separate planner or in {{VolcanoPlanner}}
> itself. The planner should take multiple SQL statements as input and return a
> unified {{RelNode}} tree.
> Example of above is as follows:
> {{SELECT COL1, COL2 FROM TABLE WHERE COL3 > 10;}}
> {{SELECT COL1, COL2 FROM TABLE WHERE COL4 = 'abc';}}
> The above 2 statements have a common path and hence can provide a unified
> {{RelNode}} tree as follows:
> {noformat}
> [Scan] -> [Project (COL1, COL2)] -> [Filter (COL4 = 'abc')] -> [Delta]
> |
> V
> [Filter (COL3 > 10)]
> |
> v
> [Delta]
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CALCITE-6258) Map value constructor is unparsed incorrectly for PrestoSqlDialect
[
https://issues.apache.org/jira/browse/CALCITE-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CALCITE-6258:
Labels: pull-request-available (was: )
> Map value constructor is unparsed incorrectly for PrestoSqlDialect
> --
>
> Key: CALCITE-6258
> URL: https://issues.apache.org/jira/browse/CALCITE-6258
> Project: Calcite
> Issue Type: Bug
>Reporter: EveyWu
>Priority: Minor
> Labels: pull-request-available
>
> Presto Map function：{{{}map{}}}({_}array{_}, {_}array{_})
> https://teradata.github.io/presto/docs/current/functions/map.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CALCITE-6258) Map value constructor is unparsed incorrectly for PrestoSqlDialect
EveyWu created CALCITE-6258:
Summary: Map value constructor is unparsed incorrectly for
PrestoSqlDialect
Key: CALCITE-6258
URL: https://issues.apache.org/jira/browse/CALCITE-6258
Project: Calcite
Issue Type: Bug
Reporter: EveyWu
Presto Map function：{{{}map{}}}({_}array{_}, {_}array{_})
https://teradata.github.io/presto/docs/current/functions/map.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CALCITE-6257) StarRocks dialect implementation
[ https://issues.apache.org/jira/browse/CALCITE-6257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CALCITE-6257: Labels: pull-request-available (was: ) > StarRocks dialect implementation > > > Key: CALCITE-6257 > URL: https://issues.apache.org/jira/browse/CALCITE-6257 > Project: Calcite > Issue Type: New Feature >Reporter: EveyWu >Priority: Minor > Labels: pull-request-available > > StarRocks has an MPP architecture and is equipped with a fully vectorized > execution engine, a columnar storage engine that supports real-time updates. > [https://docs.starrocks.io/docs/introduction/StarRocks_intro/] > At present, StarRocks has a wide range of applications. Implementing dialect > in Calcite will be valuable for many bi-services. > It closely follows MySQL but has enough differences to warrant a separate > dialect in Calcite. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CALCITE-6257) StarRocks dialect implementation
EveyWu created CALCITE-6257: Summary: StarRocks dialect implementation Key: CALCITE-6257 URL: https://issues.apache.org/jira/browse/CALCITE-6257 Project: Calcite Issue Type: New Feature Reporter: EveyWu StarRocks has an MPP architecture and is equipped with a fully vectorized execution engine, a columnar storage engine that supports real-time updates. [https://docs.starrocks.io/docs/introduction/StarRocks_intro/] At present, StarRocks has a wide range of applications. Implementing dialect in Calcite will be valuable for many bi-services. It closely follows MySQL but has enough differences to warrant a separate dialect in Calcite. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CALCITE-6243) Upgrade Cassandra to 4.1.3 and DataStax driver for Cassandra to 4.17.0
[ https://issues.apache.org/jira/browse/CALCITE-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816336#comment-17816336 ] Alessandro Solimando commented on CALCITE-6243: --- Fixed via [8fd9518|https://github.com/apache/calcite/commit/8fd9518887302af43e7e74cdb155474dcebfc9f5], thanks [~jiajunbernoulli] for the review. > Upgrade Cassandra to 4.1.3 and DataStax driver for Cassandra to 4.17.0 > -- > > Key: CALCITE-6243 > URL: https://issues.apache.org/jira/browse/CALCITE-6243 > Project: Calcite > Issue Type: Task > Components: cassandra-adapter >Affects Versions: 1.36.0 >Reporter: Alessandro Solimando >Assignee: Alessandro Solimando >Priority: Major > Labels: security > Fix For: 1.37.0 > > > Upgrading the following dependencies: > * the Cassandra version from 4.0.1 to 4.1.3 > * the DataStax Apache Cassandra driver from 4.13.0 to 4.17.0 > From 4.1.x Windows support is dropped by Cassandra (CASSANDRA-16956), so > Cassandra tests are now skipped when executing on Windows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CALCITE-6243) Upgrade Cassandra to 4.1.3 and DataStax driver for Cassandra to 4.17.0
[ https://issues.apache.org/jira/browse/CALCITE-6243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessandro Solimando resolved CALCITE-6243. --- Resolution: Fixed > Upgrade Cassandra to 4.1.3 and DataStax driver for Cassandra to 4.17.0 > -- > > Key: CALCITE-6243 > URL: https://issues.apache.org/jira/browse/CALCITE-6243 > Project: Calcite > Issue Type: Task > Components: cassandra-adapter >Affects Versions: 1.36.0 >Reporter: Alessandro Solimando >Assignee: Alessandro Solimando >Priority: Major > Labels: security > Fix For: 1.37.0 > > > Upgrading the following dependencies: > * the Cassandra version from 4.0.1 to 4.1.3 > * the DataStax Apache Cassandra driver from 4.13.0 to 4.17.0 > From 4.1.x Windows support is dropped by Cassandra (CASSANDRA-16956), so > Cassandra tests are now skipped when executing on Windows. -- This message was sent by Atlassian Jira (v8.20.10#820010)
