yihua commented on issue #6644: URL: https://github.com/apache/hudi/issues/6644#issuecomment-1254302236
@koochiswathiTR Thanks for raising this! The config naming of `partition_key` is confusing to new comers. Here's what you need to do: (1) As @xushiyan already mentioned, you don't need to set the credentials in env variables if the instance or service is already granted access with the proper roles; (2) By default, `hoodie.write.lock.dynamodb.partition_key` is set to the table name, so that multiple writers writing to the same table share the same lock. If you customize the name, make sure it's the same for multiple writers; (3) Note that, what `hoodie.write.lock.dynamodb.partition_key` specifies actually means the value to use for the column, and not the column name itself. The column name is fixed to be `key` in DynamoDB table; (4) The DynamoDB table for locking purposes is automatically created from the Hudi code, so you don't have to create the table yourself. If you do so, make sure that the `key` column is present in the table, not `lock` or the value specified by `hoodie.write.lock.dynamodb.partition_key`. Let me know if this solves your problem. Feel free to close it once all good. -- 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]
