[
https://issues.apache.org/jira/browse/FLINK-9334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-9334:
----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Docs to have a code snippet of Kafka partition discovery
> --------------------------------------------------------
>
> Key: FLINK-9334
> URL: https://issues.apache.org/jira/browse/FLINK-9334
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka
> Reporter: Juho Autio
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> Tzu-Li (Gordon) said:
> {quote}Yes, it might be helpful to have a code snippet to demonstrate the
> configuration for partition discovery.
> {quote}
>
> ----
> *Background*
>
> The docs correctly say:
>
> {quote}To enable it, set a non-negative value for
> +flink.partition-discovery.interval-millis+ in the _provided properties
> config_
> {quote}
>
> So it should be set in the Properties that are passed in the constructor of
> FlinkKafkaConsumer.
>
> I had somehow assumed that this should go to flink-conf.yaml (maybe because
> it starts with "flink."?), and obviously the FlinkKafkaConsumer doesn't read
> that.
>
> A piece of example code might've helped me avoid this mistake.
>
> This was discussed on the user mailing list:
>
> [http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Kafka-Consumers-Partition-Discovery-doesn-t-work-tp19129p19484.html]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
