You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2015/01/23 21:30:35 UTC
[jira] [Commented] (FLINK-1342) Quickstart's assembly can possibly
filter out user's code
[ https://issues.apache.org/jira/browse/FLINK-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289913#comment-14289913 ]
Fabian Hueske commented on FLINK-1342:
--------------------------------------
This is also true for all dependencies which are from the o.a.f namespace.
For example flink-hadoop-compatibility is not added to ./lib and not in Flink's class path by default.
Programs which depend on the hadoop-compat module and which are built with the quick start Maven config won't run unless the hadoop-compat jar is manually added to ./lib.
I'd suggest to only filter those dependencies which are present in ./lib even though this might end up in a rather bulky blacklist.
> Quickstart's assembly can possibly filter out user's code
> ---------------------------------------------------------
>
> Key: FLINK-1342
> URL: https://issues.apache.org/jira/browse/FLINK-1342
> Project: Flink
> Issue Type: Bug
> Affects Versions: 0.9
> Reporter: Márton Balassi
> Fix For: 0.9, 0.8.1
>
>
> I've added a quick solution for [1] for the time being. The assembly still filters out everything from the org.apache.flink namespace, so any user code placed there will be missing from the fat jar.
> If we do not use filtering at all the size of the jar goes up to almost 100 MB.
> [1] https://issues.apache.org/jira/browse/FLINK-1225
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)