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

ASF GitHub Bot commented on FLINK-4315:
---------------------------------------

GitHub user kenmy opened a pull request:

    https://github.com/apache/flink/pull/2637

    [FLINK-4315] Deprecate Hadoop dependent methods in flink-java

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kenmy/flink FLINK-4315

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2637.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2637
    
----
commit b2de2ef82a7ba5ed50782ae897691910c2154ff6
Author: Evgeny_Kincharov <[email protected]>
Date:   2016-10-14T13:19:22Z

    [FLINK-4315] Methods, connected with hadoop from flink-java and flink-scala 
are marked as depricated.
    
    This change for moving this methods into the flink-hadoop-compatibility in 
the future.

----


> Deprecate Hadoop dependent methods in flink-java
> ------------------------------------------------
>
>                 Key: FLINK-4315
>                 URL: https://issues.apache.org/jira/browse/FLINK-4315
>             Project: Flink
>          Issue Type: Task
>          Components: Java API
>            Reporter: Stephan Ewen
>            Assignee: Evgeny Kincharov
>             Fix For: 2.0.0
>
>
> The API projects should be independent of Hadoop, because Hadoop is not an 
> integral part of the Flink stack, and we should have the option to offer 
> Flink without Hadoop dependencies.
> The current batch APIs have a hard dependency on Hadoop, mainly because the 
> API has utility methods like `readHadoopFile(...)`.
> I suggest to deprecate those methods and add helpers in the 
> `flink-hadoop-compatibility` project.
> FLINK-4048 will later remove the deprecated methods.



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

Reply via email to