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

Seth Wiesman updated FLINK-22554:
---------------------------------
    Description: 
Flink's Kafka source supports subscription patterns, where it will consume all 
topics that match a specified regex and periodically monitor for new topics. We 
should support this in the statefun Kafka ingress as it is generally useful and 
would remove a source of cluster downtime (subscribing to a new topic).

 

I propose something like this.

 
{code:java}
topics:
    - topic-pattern: my-topic-* // some regex
      discovery-interval: 10s  // some duration 
      valueType: blah
      targets: 
          - blah{code}
The Flink consumer can be configured with both a list of concrete topics + a 
pattern so validation is simple.

 

cc [~igalshilman]

  was:
Flink's Kafka source supports subscription patterns, where it will consume all 
topics that match a specified regex and periodically monitor for new topics. We 
should support this in the statefun Kafka ingress as it is generally useful and 
would remove a source of cluster downtime (subscribing to a new topic).

 

I propose something like this.

 
{code:java}
topics:
    - topic-pattern: my-topic-*
      valueType: blah
      targets: 
          - blah{code}
The Flink consumer can be configured with both a list of concrete topics + a 
pattern so validation is simple.

 

cc [~igalshilman]


> Support Kafka Topic Patterns in Kafka Ingress
> ---------------------------------------------
>
>                 Key: FLINK-22554
>                 URL: https://issues.apache.org/jira/browse/FLINK-22554
>             Project: Flink
>          Issue Type: Improvement
>          Components: Stateful Functions
>    Affects Versions: statefun-3.1.0
>            Reporter: Seth Wiesman
>            Priority: Major
>
> Flink's Kafka source supports subscription patterns, where it will consume 
> all topics that match a specified regex and periodically monitor for new 
> topics. We should support this in the statefun Kafka ingress as it is 
> generally useful and would remove a source of cluster downtime (subscribing 
> to a new topic).
>  
> I propose something like this.
>  
> {code:java}
> topics:
>     - topic-pattern: my-topic-* // some regex
>       discovery-interval: 10s  // some duration 
>       valueType: blah
>       targets: 
>           - blah{code}
> The Flink consumer can be configured with both a list of concrete topics + a 
> pattern so validation is simple.
>  
> cc [~igalshilman]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to