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

ASF GitHub Bot logged work on GOBBLIN-1409:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 12/Mar/21 18:51
            Start Date: 12/Mar/21 18:51
    Worklog Time Spent: 10m 
      Work Description: milimetric opened a new pull request #3244:
URL: https://github.com/apache/gobblin/pull/3244


   Dear Gobblin maintainers,
   
   This is my first PR, please do point out any mistakes or omissions.
   
   
   ### JIRA
   [GOBBLIN-1409](https://issues.apache.org/jira/browse/GOBBLIN-1409)
   
   
   ### Description
   When consuming from Kafka, we need the kafka timestamp and timestamp type.  
This change implements the necessary methods.
   
   
   ### Tests
   - The existing test was updated to check the new methods.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 565452)
    Time Spent: 1h  (was: 50m)

> Expose Kafka timestamp via Kafka1ConsumerRecord
> -----------------------------------------------
>
>                 Key: GOBBLIN-1409
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1409
>             Project: Apache Gobblin
>          Issue Type: Improvement
>          Components: gobblin-kafka
>            Reporter: Dan Andreescu
>            Assignee: Shirshanka Das
>            Priority: Major
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> When consuming from Kafka, we need the kafka timestamp.  We weren't sure if 
> there was another way to expose this, but figured it's a general enough need 
> that it should be implemented.  And it didn't affect performance as far as we 
> could see.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to