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

Flink Jira Bot updated FLINK-27492:
-----------------------------------
    Labels: pull-request-available stale-assigned  (was: pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issue is assigned but has not 
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a 
comment updating the community on your progress.  If this issue is waiting on 
feedback, please consider this a reminder to the committer/reviewer. Flink is a 
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone 
else may work on it.


> Flink table scala example does not including the scala-api jars
> ---------------------------------------------------------------
>
>                 Key: FLINK-27492
>                 URL: https://issues.apache.org/jira/browse/FLINK-27492
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / API
>    Affects Versions: 1.15.0, 1.16.0
>            Reporter: Yun Gao
>            Assignee: Timo Walther
>            Priority: Critical
>              Labels: pull-request-available, stale-assigned
>             Fix For: 1.16.0, 1.15.2
>
>
> Currently it seems the flink-scala-api, flink-table-api-scala-bridge is not 
> including from the binary package[1]. However, currently the scala table 
> examples seems not include the scala-api classes in the generated jar, If we 
> start a standalone cluster from the binary distribution package and then 
> submit a table / sql job in scala, it would fail due to not found the 
> StreamTableEnvironment class.
>  
> [1] 
> https://nightlies.apache.org/flink/flink-docs-master/docs/dev/configuration/advanced/#anatomy-of-table-dependencies



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to