You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "kyle k (JIRA)" <ji...@apache.org> on 2017/05/19 19:23:04 UTC
[jira] [Commented] (KAFKA-3821) Allow Kafka Connect source tasks to
produce offset without writing to topics
[ https://issues.apache.org/jira/browse/KAFKA-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16017884#comment-16017884 ]
kyle k commented on KAFKA-3821:
-------------------------------
As a potential solution why can't the {{OffsetStorageWriter}}'s {{void offset(Map<String, ?> partition, Map<String, ?> offset)}} function be made available on the {{SourceTaskContext}}? This seems to me as if it would work out of the box... or am I missing something?
Additionally offsets need to be written in {{WorkerSourceTask}} after {{transformationChain.apply}} if it returns {{null}} indicating that the record should be filtered.
> Allow Kafka Connect source tasks to produce offset without writing to topics
> ----------------------------------------------------------------------------
>
> Key: KAFKA-3821
> URL: https://issues.apache.org/jira/browse/KAFKA-3821
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 0.9.0.1
> Reporter: Randall Hauch
> Labels: needs-kip
>
> Provide a way for a {{SourceTask}} implementation to record a new offset for a given partition without necessarily writing a source record to a topic.
> Consider a connector task that uses the same offset when producing an unknown number of {{SourceRecord}} objects (e.g., it is taking a snapshot of a database). Once the task completes those records, the connector wants to update the offsets (e.g., the snapshot is complete) but has no more records to be written to a topic. With this change, the task could simply supply an updated offset.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)