[
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 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.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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.3.4#803005)
