[ 
https://issues.apache.org/jira/browse/BEAM-4038?focusedWorklogId=138484&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-138484
 ]

ASF GitHub Bot logged work on BEAM-4038:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 27/Aug/18 17:21
            Start Date: 27/Aug/18 17:21
    Worklog Time Spent: 10m 
      Work Description: stale[bot] commented on issue #5287: [BEAM-4038] 
Support writing ProducerRecords to Kafka
URL: https://github.com/apache/beam/pull/5287#issuecomment-416300484
 
 
   This pull request has been marked as stale due to 60 days of inactivity. It 
will be closed in 1 week if no further activity occurs. If you think that’s 
incorrect or this pull request requires a review, please simply write any 
comment. If closed, you can revive the PR at any time and @mention a reviewer 
or discuss it on the d...@beam.apache.org list. Thank you for your 
contributions.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 138484)
    Time Spent: 9h 50m  (was: 9h 40m)

> Support Kafka Headers in KafkaIO
> --------------------------------
>
>                 Key: BEAM-4038
>                 URL: https://issues.apache.org/jira/browse/BEAM-4038
>             Project: Beam
>          Issue Type: New Feature
>          Components: io-java-kafka
>            Reporter: Geet Kumar
>            Assignee: Geet Kumar
>            Priority: Major
>          Time Spent: 9h 50m
>  Remaining Estimate: 0h
>
> Headers have been added to Kafka Consumer/Producer records (KAFKA-4208). The 
> purpose of this JIRA is to support this feature in KafkaIO.  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to