You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Seth Wiesman (Jira)" <ji...@apache.org> on 2020/04/01 20:41:00 UTC
[jira] [Commented] (FLINK-16930) Drop
StatefulFunctionsClusterEntryPoint
[ https://issues.apache.org/jira/browse/FLINK-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073167#comment-17073167 ]
Seth Wiesman commented on FLINK-16930:
--------------------------------------
We should investigate the plugin mechanism. It should allow the same api with the added benefit of keeping the class path clean.
> Drop StatefulFunctionsClusterEntryPoint
> ---------------------------------------
>
> Key: FLINK-16930
> URL: https://issues.apache.org/jira/browse/FLINK-16930
> Project: Flink
> Issue Type: Improvement
> Components: Stateful Functions
> Reporter: Igal Shilman
> Priority: Major
>
> Stateful functions is using a custom ClusterEntryPoint that is based on org.apache.flink.runtime.entrypoint.JobClusterEntrypoint.
> The reason we have our own entry point is that we need to setup the userClassPath (all the artifacts found under /opt/statefun/modules/*)
> But having our own entry point might lead to a code rot and miss important improvements (for example [1]) or bugfixes.
> This issue is to track how can we remove our custom entry point and reuse the existing ones (perhaps with enhancement)
>
> [1]https://issues.apache.org/jira/browse/FLINK-16658
--
This message was sent by Atlassian Jira
(v8.3.4#803005)