[
https://issues.apache.org/jira/browse/FLINK-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17336076#comment-17336076
]
Flink Jira Bot commented on FLINK-19538:
----------------------------------------
This issue was labeled "stale-major" 7 ago and has not received any updates so
it is being deprioritized. If this ticket is actually Major, please raise the
priority and ask a committer to assign you the issue or revive the public
discussion.
> Support more complex routers in remote ingress definitions
> ----------------------------------------------------------
>
> Key: FLINK-19538
> URL: https://issues.apache.org/jira/browse/FLINK-19538
> Project: Flink
> Issue Type: New Feature
> Components: Stateful Functions
> Reporter: Seth Wiesman
> Priority: Major
> Labels: stale-major
>
> Ingresses defined via Yaml route messages with an implicit key pulled via the
> header of the source. If users need to route based on another key they must
> either be first sent to a function that serves solely as a router and then
> forward it or write their ingress in Java. We should support more complex
> routers in Yaml.
> See ML Question:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Native-State-in-Python-Stateful-Functions-td38563.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
