You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/09/11 04:10:00 UTC

[jira] [Work logged] (GOBBLIN-1259) Implement a Kafka streaming extractor

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

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

                Author: ASF GitHub Bot
            Created on: 11/Sep/20 04:09
            Start Date: 11/Sep/20 04:09
    Worklog Time Spent: 10m 
      Work Description: sv2000 opened a new pull request #3102:
URL: https://github.com/apache/incubator-gobblin/pull/3102


   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   
   ### JIRA
   - [x] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-1259
   
   
   ### Description
   - [x] Here are some details about my PR, including screenshots (if applicable):
   This PR provides an implementation of Kafka Extractor that uses Gobblin's streaming mode.  The streaming extractor is implemented to periodically generate Flush control messages to allow the pipeline to commit the data to the destination system. For the case of Kafka-> HDFS, the Flush message serves as the logical point to commit files to the destination publish directory, and checkpointing watermarks to the state store. The extractor also tracks various statistics concerning the input source such as the (moving) average of production rate and record sizes, which will be used by the KafkaSource when computing work units. 
   
   ### Tests
   - [x] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   Added unit tests.
   
   ### Commits
   - [x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   


----------------------------------------------------------------
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:
users@infra.apache.org


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

            Worklog Id:     (was: 481882)
    Remaining Estimate: 0h
            Time Spent: 10m

> Implement a Kafka streaming extractor
> -------------------------------------
>
>                 Key: GOBBLIN-1259
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1259
>             Project: Apache Gobblin
>          Issue Type: Improvement
>          Components: gobblin-kafka
>    Affects Versions: 0.16.0
>            Reporter: Sudarshan Vasudevan
>            Assignee: Shirshanka Das
>            Priority: Major
>             Fix For: 0.16.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> This PR provides an implementation of Kafka Extractor that uses Gobblin's streaming mode. 



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