[
https://issues.apache.org/jira/browse/FLINK-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-19538:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
