[
https://issues.apache.org/jira/browse/FLINK-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002672#comment-16002672
]
Xingcan Cui commented on FLINK-6247:
------------------------------------
Hi [~fhueske], as long as it doesn't matter for the target jar, I think this
should be the most direct and effective solution. :)
> Build a jar-with-dependencies for flink-table and put it into ./opt
> -------------------------------------------------------------------
>
> Key: FLINK-6247
> URL: https://issues.apache.org/jira/browse/FLINK-6247
> Project: Flink
> Issue Type: Improvement
> Components: Build System, Table API & SQL
> Affects Versions: 1.3.0
> Reporter: Fabian Hueske
> Assignee: sunjincheng
> Fix For: 1.3.0
>
>
> Due to a problem with Calcite and the unloading of classes, user-code
> classloaders that include Calcite cannot be garbage collected. This is a
> problem for long-running clusters that execute multiple Table API / SQL
> programs with fat JARs that include the flink-table dependency. Each executed
> program comes with an own user-code classloader that cannot be cleaned up
> later.
> As a workaround, we recommend to copy the flink-table dependency into the
> ./lib folder. However, we do not have a jar file with all required transitive
> dependencies (Calcite, Janino, etc). Hence, users would need to build this
> jar file themselves or copy all jars into ./lib.
> This issue is about creating a jar-with-dependencies and adding it to the
> ./opt folder. Users can then copy the jar file from ./opt to ./lib to include
> the table API in the classpath of Flink.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
