-
Notifications
You must be signed in to change notification settings - Fork 2.5k
fix: aws glue sync set comment #14234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
yihua
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Possible to add a test case on this?
|
bb2fda9 to
abf8e3d
Compare
locally i run the IT with spark profile 3.3 successfuly. The CI run spark 3.5. Sounds like there is a parquet deps conflict on this profile |
5d5d659 to
7bafc7a
Compare
fix problem with array fix array of struct
|
@yihua I added a test framework that will be useful to validate the aws binding. what about landing this fix into 1.1 ? |
|
also maybe @danny0405 ? |
|
There is a test failure: [ERROR] Errors:
[ERROR] TestAwsGlueSyncTool.validateInitThroughSyncTool:96 » Hoodie Unable to instanti... |
|
|
||
| private void setComments(List<Column> columns, Map<String, Option<String>> commentsMap) { | ||
| columns.forEach(column -> { | ||
| private List<Column> setComments(List<Column> columns, Map<String, Option<String>> commentsMap) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The original logic does not take any effect right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's the point. BTW the test did prove the original method fail. New implem fixes the tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you fix the test failures.
| ) | ||
| .build()) | ||
| .build()).build()).get(); | ||
| public void setUpPushdownTest() throws Exception { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so we can ensure the super class setUp() been executed before this one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The answer is true if the method is not overidden.
danny0405
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, let's fix the test failures.
add tests fix deps restore partition pushd down it fix checkstyle fix test
7bafc7a to
5613bfe
Compare
|
@danny0405 i fixed the tests, let wait the CI to confirm. Note that without #14235 the comments still won't be added. The reason is the comments are coming from the |
| </image> | ||
| <image> | ||
| <name>apachehudi/moto:${moto.version}</name> | ||
| <name>motoserver/moto:${moto.version}</name> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure what the exact effect of the change
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The hudi image is not cross platform. Only amd64. The motoserver is cross platform. Not sure whonisballowednto push hudi images to dockerhub
| <name>amazon/dynamodb-local:${dynamodb-local.version}</name> | ||
| <alias>it-database</alias> | ||
| <run> | ||
| <platform>linux/amd64</platform> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why remove this
| <name>motoserver/moto:${moto.version}</name> | ||
| <alias>it-aws</alias> | ||
| <run> | ||
| <platform>linux/amd64</platform> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why remove this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes the image agnostic to the platform. Pining to amd64 did not allow to run the test on arm64 or apple silicon
|
@hudi-bot run azure |
|
@hudi-bot run azure |
|
@parisni can you retrigger this PR CI by a dummy commit, I can not trigger it through the cmd. |
|
@danny0405 done. also in the other PR |
|
@hudi-bot run azure |
yihua
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@parisni Could you rebase your branch on top of the latest master? A few fixes on CI flakiness have been merged.
yihua
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall. @parisni Could you check CI failures and rebase the PR on master?
|
Hi @yihua @danny0405 i did again rebase on master. |
Describe the issue this Pull Request addresses
the #9347 PR introduced a regression on the aws glue comments when moving to the aws sdk v2. This restore the original behavior
Summary and Changelog
Impact
Risk Level
Documentation Update
Contributor's checklist