You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/05/21 12:18:04 UTC

[jira] [Closed] (FLINK-8437) SideOutput() API is ambiguous

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

Flink Jira Bot closed FLINK-8437.
---------------------------------
    Resolution: Auto Closed

This issue was labeled "stale-minor" 7 ago and has not received any updates so I have gone ahead and closed it.  If you are still affected by this or would like to raise the priority of this ticket please re-open, removing the label "auto-closed" and raise the ticket priority accordingly.


> SideOutput() API is ambiguous
> -----------------------------
>
>                 Key: FLINK-8437
>                 URL: https://issues.apache.org/jira/browse/FLINK-8437
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataStream
>    Affects Versions: 1.5.0
>            Reporter: Chesnay Schepler
>            Assignee: Chen Qin
>            Priority: Minor
>              Labels: auto-closed, stale-assigned
>
> The current API for retrieving Side Outputs is a bit ambiguous. Consider the program below:
> {code:java}
> sideOutput = stream
>     .process(...)
>     .filter(...)
>     .getSideOutput(tag)
> {code}
> This may be the sideOutput of the process function that is passed through the API for convenience, or the sideOutput of the filter function (which would always be empty).
> Given that only process functions can have sideOutputs we may want to change the return type so that getSideOutput can only be called after a process function.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)