Skip to content

Conversation

@xushiyan
Copy link
Member

@xushiyan xushiyan commented Mar 20, 2022

Add AWS Glue sync implementation to allow sync to AWS Glue catalog directly via AWS SDK APIs.

@xushiyan
Copy link
Member Author

Screen Shot 2022-03-21 at 10 48 00 PM

Verified running meta sync with org.apache.hudi.aws.sync.AwsGlueCatalogSyncTool and sync'ed to Glue table.

@xushiyan xushiyan force-pushed the HUDI-2757-glue-sync branch from b7d2409 to 7bb94c0 Compare March 21, 2022 17:28
@apache apache deleted a comment from hudi-bot Mar 21, 2022
Copy link
Contributor

@nsivabalan nsivabalan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

few minor comments. looks good mostly.

@nsivabalan nsivabalan self-assigned this Mar 21, 2022
@xushiyan xushiyan force-pushed the HUDI-2757-glue-sync branch 2 times, most recently from 5b94cea to a115917 Compare March 26, 2022 11:54
@xushiyan xushiyan marked this pull request as ready for review March 26, 2022 11:54
@xushiyan xushiyan requested a review from nsivabalan March 26, 2022 11:54
Copy link
Contributor

@nsivabalan nsivabalan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, we can't write any tests for AWSGlueCatalogSync is it. if we mock, we have to mock pretty much everything and there is no point in testing only. is my understanding right.

mostly minor comments. once addressed, we can land.

}

@Override
public void updateLastCommitTimeSynced(String tableName) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A general question about updating HOODIE_LAST_COMMIT_TIME_SYNC. I see in HiveSyncTool, we call hoodieHiveClient.updateLastCommitTimeSynced(tableName)
in the end.
But updating partitions and updating the last commit time synced is not atomic. and within updateLastCommitTimeSynced, we get the latest commit time from activetimeline and update it as the lastCommitTimeSycned.
So, incase of multi-writers, there are chances that timeline has moved between updating partitions and calling updateLastCommitTimeSynced.

may be we should file a jira and do a follow up on the logic.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yea, should be a follow up item

@xushiyan xushiyan force-pushed the HUDI-2757-glue-sync branch from a115917 to 51879ca Compare March 28, 2022 14:28
Copy link
Contributor

@nsivabalan nsivabalan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rmahindra123
Copy link
Contributor

lgtm. Approved.

@hudi-bot
Copy link
Collaborator

CI report:

Bot commands @hudi-bot supports the following commands:
  • @hudi-bot run azure re-run the last Azure build

@nsivabalan nsivabalan merged commit 6ccbae4 into apache:master Mar 28, 2022
@xushiyan xushiyan deleted the HUDI-2757-glue-sync branch March 29, 2022 13:50
vingov pushed a commit to vingov/hudi that referenced this pull request Apr 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority:blocker Production down; release blocker

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants