[
https://issues.apache.org/jira/browse/HUDI-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392723#comment-17392723
]
Vinoth Chandar commented on HUDI-2199:
--------------------------------------
> it creates a table for each table name ingested or it uses a generic table
> for table ingested into hudi ?
IMO, having separate tables is better for manageability.
[https://github.com/apache/hudi/blob/master/hudi-client/hudi-spark-client/src/main/java/org/apache/hudi/index/hbase/SparkHoodieHBaseIndex.java]
here you go!
> DynamoDB based external index implementation
> --------------------------------------------
>
> Key: HUDI-2199
> URL: https://issues.apache.org/jira/browse/HUDI-2199
> Project: Apache Hudi
> Issue Type: New Feature
> Components: Index
> Reporter: Vinoth Chandar
> Assignee: Biswajit mohapatra
> Priority: Major
>
> We have a HBaseIndex, that provides uses with ability to store fileID <=>
> recordKey mappings in an external kv store, for fast lookups during upsert
> operations. We can potentially create a similar one for DynamoDB.
> We just use a single column family in HBase, so we should be able to largely
> re-use the code/key-value schema across them even.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)