You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "tison (Jira)" <ji...@apache.org> on 2019/09/25 16:17:00 UTC

[jira] [Resolved] (FLINK-14114) Shift down ClusterClient#timeout to RestClusterClient

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

tison resolved FLINK-14114.
---------------------------
    Resolution: Fixed

master via ca56b63c37176dabf163b745d6ee015012531243

> Shift down ClusterClient#timeout to RestClusterClient
> -----------------------------------------------------
>
>                 Key: FLINK-14114
>                 URL: https://issues.apache.org/jira/browse/FLINK-14114
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Client / Job Submission
>            Reporter: tison
>            Assignee: Zhu Zhu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> {{ClusterClient#timeout}} is only used in {{RestClusterClient}}, even without this prerequisite we can always shift down {{timeout}} field to subclasses of {{ClusterClient}}. It is towards an interface-ized {{ClusterClient}}. By side effect, we could reduce the dependency to parsing duration with Scala Duration on the fly.
> CC [~till.rohrmann] [~zhuzh]



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