abhisheknath2011 opened a new pull request #3328:
URL: https://github.com/apache/gobblin/pull/3328


   Avro 1.9 upgrade HI: 
https://jira01.corp.linkedin.com:8443/browse/DEPEND-15444
   Avro upgrade wiki: 
https://iwww.corp.linkedin.com/wiki/cf/pages/viewpage.action?spaceKey=ENGS&title=Avro+Initiative+2021
   Highlights from Avro 1.9 upgrade: 
https://godatadriven.com/blog/highlights-from-the-new-apache-avro-1-9-0-release/
   
   Below are some of the high level changes in Avro 1.9 (based on above 
highlight and initial investigation)
   1. Deprecation of Joda time librarty and usage of Java 8 library.
   2. Move from Jackson 1.x to 2.9. As part of this Jackson classes are removed 
from the public API. All the public method dealing with older version of 
Jackson are removed. 
      Below are some of methods no longer available
      - getJsonProps of Scheam, Schema.Field is no longer public.
      - getJsonProp of Schema, Scheam.Field is no longer available
   3. Changes related to Schema.Field default value. The "defaultValue" method 
of Schema.field is no longer available and is replaced by "defaultVal" method
   4. Avro 1.9 is leaner now and all avro shaded google guava libararies are 
removed.
   5. There are bunch of tests failing. Some of the tests are fixed and for 
some TODO list is added in the test itself.
   6. There are still lot more unidentified failed tests.
   7. To fix some of the tests is required to fix some of the existing Gobblin 
classes.
   8. Some of the tests are failing due to Helix, Hadoop, Hive libraries are 
using older Jackson version.
   9. Some of the tests are failing due to handling of NULL values in the 
schema.
   10. This is a bigger change and breaking change and more analysis and 
discussion is required. 


-- 
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