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

["nsivabalan (via GitHub)" <gi...@apache.org>]

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

   @Limess : 
   Are you setting "hoodie.table.name" in your write configs? this is our infer fuction
   ```
    public static final ConfigProperty<String> DYNAMODB_LOCK_PARTITION_KEY = ConfigProperty
         .key(DYNAMODB_BASED_LOCK_PROPERTY_PREFIX + "partition_key")
         .noDefaultValue()
         .sinceVersion("0.10.0")
         .withInferFunction(cfg -> {
           if (cfg.contains(HoodieTableConfig.NAME)) {
             return Option.of(cfg.getString(HoodieTableConfig.NAME));
           }
           return Option.empty();
         })
         .withDocumentation("For DynamoDB based lock provider, the partition key for the DynamoDB lock table. "
                            + "Each Hudi dataset should has it's unique key so concurrent writers could refer to the same partition key."
                            + " By default we use the Hudi table name specified to be the partition key");
   ```
   
   


-- 
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