Hans-Raintree opened a new issue, #13333:
URL: https://github.com/apache/hudi/issues/13333

   **Describe the problem you faced**
   
   I've set hoodie.embed.timeline.server=false in Flink Hudi sink options, but 
timeline is still created.
   
   Why I'm disabling it is because AWS Managed Flink doesn't support it:
   
https://docs.aws.amazon.com/managed-flink/latest/java/troubleshooting-hudi.html
   
   Also I'm trying to backfill from a separate spark job and do table services 
via separate spark job, so I think timeline wouldn't be supported in this 
scenario anyway?
   
   Also I get the following error, not sure if it's related to the 
timeline.server:
   
   Caused by: org.apache.hudi.exception.HoodieException: Unable to instantiate 
class org.apache.hudi.client.transaction.lock.FileSystemBasedLockProvider
   Caused by: org.apache.hudi.exception.HoodieLockException: Unsupported scheme 
:s3a, since this fs can not support atomic creation
        at 
org.apache.hudi.client.transaction.lock.FileSystemBasedLockProvider.<init>(FileSystemBasedLockProvider.java:89)
        ... 22 more
   
   Although I have 'NON_BLOCKING_CONCURRENCY_CONTROL' enabled, I had to 
additionally set hoodie.write.lock.provider to DynamoDBBasedLockProvider, to 
get around that error.
   
   **To Reproduce**
   
   Steps to reproduce the behavior:
   
   1. Create a Flink Application with Hudi Sink Configuration 
hoodie.embed.timeline.server=false
   2. Timeline is still created.
   
   **Expected behavior**
   
   Timeline is disabled.
   
   **Environment Description**
   
   * Hudi version : 1.0.2
   
   * Spark version : -
   
   * Hive version : -
   
   * Hadoop version : -
   
   * Storage (HDFS/S3/GCS..) : S3
   
   * Running on Docker? (yes/no) : no


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

Reply via email to