[
https://issues.apache.org/jira/browse/FLINK-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342921#comment-17342921
]
Seth Wiesman commented on FLINK-16930:
--------------------------------------
[~igal] The major benefits are being able to more readily leverage advancements
in Flinks resource manager's and scheduler. Dropping the entry point would
allow deploying using the native K8s resource manager and leveraging the
reactive scheduler once StateFun supports 1.13.
> 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: Minor
> Labels: auto-deprioritized-major
> Fix For: statefun-3.1.0
>
>
> 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)
