[
https://issues.apache.org/jira/browse/FLINK-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6607:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
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
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Confusing statement in docs that Kafka 010 consumer does not require
> timestamp extractors
> -----------------------------------------------------------------------------------------
>
> Key: FLINK-6607
> URL: https://issues.apache.org/jira/browse/FLINK-6607
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Kafka, Documentation
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> In
> https://ci.apache.org/projects/flink/flink-docs-release-1.2/dev/connectors/kafka.html#using-kafka-timestamps-and-flink-event-time-in-kafka-010,
> the docs state that the Kafka 010 consumer does not require timestamp
> extractors because the Kafka records' timestamps can be used.
> While this is true, it is confusing for the Kafka 010 consumer because
> currently timestamp extraction and watermark generating is bound to a single
> `AssignerWithXXXWatermarks` interface. This may cause users to misunderstand
> that even watermark generating isn't required also.
> We perhaps should strengthen the clarification of this a bit more in that
> part of the docs to avoid confusion.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
