flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sunjincheng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-11067) Port TableEnvironments to Java
Date Wed, 12 Dec 2018 06:37:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-11067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16718513#comment-16718513
] 

sunjincheng commented on FLINK-11067:
-------------------------------------

We list the two ways users use BatchTableEnvironment, as follows:
 1.Using api.scala.BatchTableEnvironment
{code:java}
import org.apache.flink.table.api.scala.BatchTableEnvironment
BatchTableEnvironment tEnv = 
 TableEnvironment.getTableEnvironment(env);
{code}
2. api.java.BatchTableEnvironment
 BatchTableEnvironment tEnv =
{code:java}
import org.apache.flink.table.api.java.BatchTableEnvironment
BatchTableEnvironment tEnv = 
 TableEnvironment.getTableEnvironment(env);
{code}
According to current design, `flink-tabe-api-java/flink-tabe-api-scala` dependent the `flink-tabe-api-base`,
then the `api.java.BatchTableEnvironment` and `api.scala.BatchTableEnvironment` can not be
import in `flink-tabe-api-base`,So I also want to know [~dian.fu]'s question that which
package does `BatchTableEnvironment` belong to, in `getTableEnvironment()` definition?
{code:java}
static BatchTableEnvironment getTableEnvironment(BatchEnvironment env);
{code}

Bests,
Jincheng


> Port TableEnvironments to Java
> ------------------------------
>
>                 Key: FLINK-11067
>                 URL: https://issues.apache.org/jira/browse/FLINK-11067
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table API &amp; SQL
>            Reporter: Timo Walther
>            Assignee: Dawid Wysakowicz
>            Priority: Major
>
> This task includes porting {{TableEnvironment}}, {{StreamTableEnvironment}}, {{BatchTableEnvironment}}
to Java. API-breaking changes need to be avoided and discussed. Some refactoring and clean
up might be necessary.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message