[jira] [Comment Edited] (FLINK-19538) Support more complex routers in remote ingress definitions

["Seth Wiesman (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-19538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17216726#comment-17216726 ] 

Seth Wiesman edited comment on FLINK-19538 at 10/19/20, 1:42 PM:
-----------------------------------------------------------------

I've gone back and forth since opening this ticket. I suspect the long term need is for proper remote routers and probably also remote (de)serializers. I need to think about this more. 


was (Author: sjwiesman):
I've gone back and forth since opening this ticket and I'm not really sure what I want. I think this is going to be a longer conversation. 

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