[
https://issues.apache.org/jira/browse/KAFKA-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989790#comment-15989790
]
ASF GitHub Bot commented on KAFKA-5142:
---------------------------------------
GitHub user michaelandrepearce opened a pull request:
https://github.com/apache/kafka/pull/2942
KAFKA-5142: Expose Record Headers in Kafka Connect
as per KIP-145
Add constructors to Connect/Source/SinkRecord to take Iterable<Header>
add accessor method to ConnectRecord "Headers headers()"
Update WorkerSource/Sink to pass headers to/from Producer/ConsumerRecords
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/IG-Group/kafka KIP-145
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2942.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2942
----
commit 535ea20b63be67463d822530af95e535b020dd45
Author: Michael Andre Pearce <[email protected]>
Date: 2017-04-29T07:05:05Z
KAFKA-5142: Expose Record Headers in Kafka Connect
as per KIP-145
Add constructors to Connect/Source/SinkRecord to take Iterable<Header>
add accessor method to ConnectRecord "Headers headers()"
Update WorkerSource/Sink to pass headers to/from Producer/ConsumerRecords
----
> KIP-145 - Expose Record Headers in Kafka Connect
> ------------------------------------------------
>
> Key: KAFKA-5142
> URL: https://issues.apache.org/jira/browse/KAFKA-5142
> Project: Kafka
> Issue Type: New Feature
> Components: clients
> Reporter: Michael Andre Pearce (IG)
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-145+-+Expose+Record+Headers+in+Kafka+Connect
> As KIP-82 introduced Headers into the core Kafka Product, it would be
> advantageous to expose them in the Kafka Connect Framework.
> Connectors that replicate data between Kafka cluster or between other
> messaging products and Kafka would want to replicate the headers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)