pedro93 opened a new pull request #3455:
URL: https://github.com/apache/gobblin/pull/3455


   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-XXX
   
   
   ### Description
   Gobblin depended on an old deprecated Avro API that worked with Jackson 
JsonNode objects. In Gobblin's default Avro dependency version (1.8) these APIs 
were already marked as deprecated. In Avro 1.9 these APIs were replaced by 
similar APIs that work with `Object` rather than `JsonNode` Java objects.
   
   ### Tests
   My PR does not need unit tests to validate whether it is working. Simply 
attempting to compile the project with a flag to inject avro 1.9+ 
(`-PavroVersion=1.9.1`) validates that this PR fixes the issue.
   Functionally the change also worked appropriately as I was able to use newer 
Avro versions to read events from Kafka using gobblin jobs that depended on 
these new versions.
   
   ### 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.

To unsubscribe, e-mail: [email protected]

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


Reply via email to