[ 
https://issues.apache.org/jira/browse/FLINK-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Flink Jira Bot updated FLINK-19538:
-----------------------------------
    Priority: Minor  (was: Major)

> 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
>
> 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)

Reply via email to