meethngala opened a new pull request, #3697:
URL: https://github.com/apache/gobblin/pull/3697

   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-XXX
   
   
   ### Description
   I want to upgrade our iceberg version to 1.2.0 to leverage performance 
improvements such as optimized metadata caching, reduced memory consumption, 
and faster metadata commits, enhanced APIs, schema evolution. Most importantly 
it natively provides support for Apache Spark 3.x, allowing seamless 
integration and improved performance when using Iceberg with Spark. As part of 
this upgrade, below are the major changes:
   - Update method signatures for `CatalogUtil.loadCatalog()` and 
`Snapshots.allManifests`
   - Initialize and load `HiveCatalog` via `CatalogUtil` inside 
`IcebergMetadataWriter` 
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   - Updated unit tests
   - Successful Build
   
   ### 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]

Reply via email to