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 2022/01/01 22:39:00 UTC

[jira] [Updated] (FLINK-7016) Move inputFormat to InputFormatVertex from TaskConfig

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

Flink Jira Bot updated FLINK-7016:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned  (was: auto-deprioritized-major auto-unassigned stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> Move inputFormat to InputFormatVertex from TaskConfig
> -----------------------------------------------------
>
>                 Key: FLINK-7016
>                 URL: https://issues.apache.org/jira/browse/FLINK-7016
>             Project: Flink
>          Issue Type: Improvement
>          Components: API / DataSet, API / DataStream
>            Reporter: Xu Pingyong
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, auto-unassigned
>
> On batch case, InputFormat is put into TaskConfig, batch task gets it to read data and job manager uses it to split splits from TaskConfig.
> On streaming case, all configs are put into StreamConfig, but this inputFormat is put into TaskConfig.
> We can put InputFormat into InputFormatVertex, and batch task still gets InputFormat from TaskConfig. It will be clear.



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