[jira] [Updated] (FLINK-14757) scala.StreamExecutionEnvironment Doesn't set return type upon adding source

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-14757:
-----------------------------------
    Labels: auto-deprioritized-major stale-minor  (was: auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> scala.StreamExecutionEnvironment Doesn't set return type upon adding source
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-14757
>                 URL: https://issues.apache.org/jira/browse/FLINK-14757
>             Project: Flink
>          Issue Type: Bug
>          Components: API / Scala
>    Affects Versions: 1.9.0, 1.9.1
>            Reporter: Tim Bess
>            Priority: Minor
>              Labels: auto-deprioritized-major, stale-minor
>
> [This line|https://github.com/apache/flink/blob/d36ce5ff77fae2b01b8fbe8e5c15d610de8ed9f5/flink-streaming-scala/src/main/scala/org/apache/flink/streaming/api/scala/StreamExecutionEnvironment.scala#L618] in StreamExecutionEnvironment.scala was changed to remove the `returns` call starting in version 1.9.0. This causes subsequent transformations on the stream to fail since the return TypeInformation isn't set anymore.
>  
> Looks like the change was made in [this pr|https://github.com/apache/flink/pull/8914]. Guessing it was a mistake unless there's some reason to do this that I'm not understanding.
>  
> I'm willing to make the PR to fix it, just need it changed so we can start upgrading our microservices to 1.9.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)