Will-Lo opened a new pull request, #4056:
URL: https://github.com/apache/gobblin/pull/4056

   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-2157
   
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if 
applicable):
   The existing iceberg registration step has the following snippet:
   ```
       if (dstMetadata != null) {
         // use current destination metadata as 'base metadata' and source as 
'updated metadata' while committing
         this.tableOps.commit(dstMetadata, 
srcMetadata.replaceProperties(dstMetadata.properties())); <<<<<------- BUG
       }
   ```
   Since Iceberg's `replaceProperties` 
https://github.com/apache/iceberg/blob/e449d3405cfdb304c94835845bd8f34a73b4a517/core/src/main/java/org/apache/iceberg/TableMetadata.java#L583
 just replaces the full set of properties, not just any existing properties, 
the result is that all of the properties are equivalent to the destination 
table metadata properties. Which effectively copies no properties.
   
   This PR modifies this behavior so that the destination table properties can 
be overwritten by the source table properties if the source table updates 
existing properties, as well as maintaining any existing properties in the 
destination that is not defined on the source.
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for 
this extremely good reason:
   Unit tests
   
   ### 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: dev-unsubscr...@gobblin.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to