[
https://issues.apache.org/jira/browse/FLINK-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16930:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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, stale-minor
>
> 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.20.1#820001)
