-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[SUPPORT] AWSDmsAvroPayload does not work correctly with any version above 0.10.0 #6552
Comments
Configuration looks fine to me, except you don't really need to set
|
Thank you for your quick reply. It doesn't seem to be either of those options for this scenario. I created a unit test and added the full code so you can understand our use case better:
This runs succesfully with Hudi 0.10.0:
and fails with Hudi 0.12.0:
Please let me know if you need any other information. |
This appears to be genuine issue introduced with ba4e732. |
Currently investigating this issue |
yeah. Udit pointed out the right commit.
|
@rahil-c and I discussed this today. The proper fix is to call the corresponding API instead of repeating the invocation of
@rahil-c will put up a fix. |
Draft pr: #6637 |
closing this as we have a fix. thanks for reporting. |
Describe the problem you faced
We are getting Full Load + CDC data from a RDBMS using AWS Database Migration Service into an S3 bucket. We then use Hudi in a Scala Glue Job to concatenate the files into a correct representation of the current status of the database. DMS adds two columns to the data: Op (with values null, I, U or D) and ts (timestamp of the operation). We are not using Hive or Avro.
This works fine with Hudi 0.9.0 and Hudi 0.10.0. Once we try to upgrade to Hudi 0.11.0, 0.11.1 or 0.12.0, AWSDmsAvroPayload fails with the following error:
Removing the PAYLOAD_CLASS_OPT_KEY option from the config makes it so that the Job doesn't fail, but the delete operations are not applied. No other payload class seems to work with the DMS format.
Steps to reproduce the behavior
Dependencies:
Configuration used:
Following options are added if a partition key is defined:
Saved into a file:
Expected behavior
Data obtained from using Hudi reflects the data present in the DB.
Environment Description
The text was updated successfully, but these errors were encountered: