flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vasia Kalavri (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-3221) Move Table API on top of Apache Calcite
Date Fri, 18 Mar 2016 14:02:33 GMT

     [ https://issues.apache.org/jira/browse/FLINK-3221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Vasia Kalavri resolved FLINK-3221.
       Resolution: Implemented
    Fix Version/s: 1.1.0

> Move Table API on top of Apache Calcite
> ---------------------------------------
>                 Key: FLINK-3221
>                 URL: https://issues.apache.org/jira/browse/FLINK-3221
>             Project: Flink
>          Issue Type: Task
>          Components: Table API
>            Reporter: Fabian Hueske
>              Labels: requires-design-doc
>             Fix For: 1.1.0
> The goal of this task is to move the Table API on top of Calcite and preserve the feature
set of the batch part. Calcite is a SQL optimization and translation framework. It includes
a SQL Parser, a catalog component, a validator, and a rule-based (relational) optimizer. This
is the first step for adding SQL and StreamSQL support to Flink.
> Since the streaming part of the Table API is rather a proof-of-concept implementation
and only features selection and projection, we exclude it from this task. With the current
Table API, queries can only be embedded into DataSet (or DataStream) programs with manually
defined schema for DataSet/DataStreams. We do not add support for external data stores (CSV,
Parquet, ORC files, HBase, etc.) as part of this task. Instead we only consume data that comes
from a DataSet/DataStream operator.
> More details can be found in the design document for SQL / StreamSQL on Flink.

This message was sent by Atlassian JIRA

View raw message