You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2019/01/18 13:42:00 UTC

[jira] [Commented] (FLINK-11028) Disable deployment of flink-fs-tests

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

Stephan Ewen commented on FLINK-11028:
--------------------------------------

Agreed, short term solution is deploy skip.

This module should go in the future, though, in my opinion. It is breaking through abstractions.

Most of the tests should not need to test against HDFS but work equally well against local fs (that is the point of the FS abstraction). If we explicitly need HDFS in the equation, then this would be even better as an end-to-end test.

Let's wait for the new source interface, which should refactor the file monitoring source.
In the meantime, we can move the remaining ones.

> Disable deployment of flink-fs-tests
> ------------------------------------
>
>                 Key: FLINK-11028
>                 URL: https://issues.apache.org/jira/browse/FLINK-11028
>             Project: Flink
>          Issue Type: Improvement
>          Components: Build System
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>             Fix For: 1.8.0
>
>
> The {{flink-fs-tests}} module only contains tests, without any production code or test utilities. As such there should never be a use-case where one would specify a dependency on this module, hence we could skip the deployment entirely.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)