flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3777) Add open and close methods to manage IF lifecycle
Date Mon, 06 Jun 2016 14:53:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15316599#comment-15316599
] 

Chesnay Schepler commented on FLINK-3777:
-----------------------------------------

small addition: there's some work being done regarding InputFormats in the Python API that
also leverage these new methods.

> Add open and close methods to manage IF lifecycle
> -------------------------------------------------
>
>                 Key: FLINK-3777
>                 URL: https://issues.apache.org/jira/browse/FLINK-3777
>             Project: Flink
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.1
>            Reporter: Flavio Pompermaier
>            Assignee: Flavio Pompermaier
>              Labels: inputformat, lifecycle
>
> At the moment the opening and closing of an inputFormat are not managed, although open()
could be (improperly IMHO) simulated by configure().
> This limits the possibility to reuse expensive resources (like database connections)
and manage their release. 
> Probably the best option would be to add 2 methods (i.e. openInputformat() and closeInputFormat()
) to RichInputFormat*
> * NOTE: the best option from a "semantic" point of view would be to rename the current
open() and close() to openSplit() and closeSplit() respectively while using open() and close()
methods for the IF lifecycle management, but this would cause a backward compatibility issue...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message