ZihanLi58 opened a new pull request #3372: URL: https://github.com/apache/gobblin/pull/3372
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 - [ ] 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-1521 ### Description - [ ] Here are some details about my PR, including screenshots (if applicable): Using embedded gobblin to run streaming job, and create a guid to help user quickly onboard * Change kafka09ConsumerClient to make get earliest and latest offset won't change the current position of the consumer, and support assignAndSeek() method * Change FsStateStore rename method to enable overwrite so that we can write to existing state store * Change reference in kafka-hdfs-streaming-avro.job to OSS class to give user better idea about how the config looks like if they want to ingest as avro, although we don't use that config in this local job since we don't have schema registry setup. * change KafkaStreamingExtractor to support the scenario where schemaRegistry is not setup ### Tests - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: Test we can run the job locally ### Commits - [ ] 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
