You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "ad1happy2go (via GitHub)" <gi...@apache.org> on 2023/05/24 12:53:14 UTC

[GitHub] [hudi] ad1happy2go commented on issue #8129: [SUPPORT] hoodie.write.lock.dynamodb.partition_key not set automatically

ad1happy2go commented on issue #8129:
URL: https://github.com/apache/hudi/issues/8129#issuecomment-1561091060

   @Limess I was able to test dynamos with 0.12 and 0.13 versions of hudi with EMR and Glue (3.0 and 4.0) with the following configurations.
   I did face this error when I have not provided the proper dynamo db access to IAM role.
   
   ```
       'hoodie.write.lock.dynamodb.endpoint_url': 'dynamodb.us-east-2.amazonaws.com',
       'hoodie.write.lock.provider': 'org.apache.hudi.aws.transaction.lock.DynamoDBBasedLockProvider',
       'hoodie.write.lock.dynamodb.table': 'aditya_github_issues_testing',
       'hoodie.write.lock.dynamodb.partition_key': 'tablename',
       'hoodie.write.lock.dynamodb.region': 'us-east-2',
       'hoodie.write.concurrency.mode':'optimistic_concurrency_control',
       'hoodie.cleaner.policy.failed.writes':'LAZY'
   ```
   
   Let me know if you still face this error. 


-- 
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: commits-unsubscribe@hudi.apache.org

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