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

Fabian Hueske updated FLINK-4315:
---------------------------------
    Description: 
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.

  was:
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 remove those methods and instead add helpers in the 
`flink-hadoop-compatibility` project.


> 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