You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hudi.apache.org by "sivabalan narayanan (Jira)" <ji...@apache.org> on 2022/01/23 19:56:00 UTC
[jira] [Commented] (HUDI-2173) Enhancing DynamoDB based LockProvider
[ https://issues.apache.org/jira/browse/HUDI-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17480724#comment-17480724 ]
sivabalan narayanan commented on HUDI-2173:
-------------------------------------------
[~dave_hagman] : Did you get a chance to check out the dynamoDB based lock provider support in master. Can you revisit your asks and update with what makes sense w/ latest code base.
> Enhancing DynamoDB based LockProvider
> -------------------------------------
>
> Key: HUDI-2173
> URL: https://issues.apache.org/jira/browse/HUDI-2173
> Project: Apache Hudi
> Issue Type: Task
> Components: writer-core
> Reporter: Vinoth Chandar
> Assignee: Dave Hagman
> Priority: Major
> Fix For: 0.11.0
>
>
> Currently, we have ZK and HMS based Lock providers, which can be limited to co-ordinating across a single EMR or Hadoop cluster.
> For aws users, DynamoDB is a readily available , fully managed , geo replicated datastore, that can actually be used to hold locks, that can now span across EMR/hadoop clusters.
> This effort involves supporting a new `DynamoDB` lock provider that implements org.apache.hudi.common.lock.LockProvider. We can place the implementation itself in hudi-client-common, so it can be used across Spark, Flink, Deltastreamer etc.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)