You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (Jira)" <ji...@apache.org> on 2020/10/19 05:40:00 UTC

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

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

Tzu-Li (Gordon) Tai commented on FLINK-19538:
---------------------------------------------

We actually do have something like that already, see the {{ProtobufRouter}}:
https://github.com/apache/flink-statefun/blob/8ffe619a94917d676cf1054c8a0e60de544663db/statefun-flink/statefun-flink-core/src/main/java/org/apache/flink/statefun/flink/core/protorouter/ProtobufRouter.java
https://github.com/apache/flink-statefun/blob/master/statefun-flink/statefun-flink-core/src/test/resources/module-v2_0/module.yaml#L54

It allows a textual definition of a Protobuf message's target address by selecting fields from the message.

AFAIK, we decided not to advertise this in the documents (and even considered removing it) because of how much more complex it is use compared to the auto-routable Kafka ingress, for example to use this, users would have to add the Protobuf descriptors of the input types into the classpaths.
We should maybe reconsider this though.


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