[
https://issues.apache.org/jira/browse/HADOOP-13908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HADOOP-13908:
-----------------------------------
Resolution: Fixed
Fix Version/s: HADOOP-13345
Status: Resolved (was: Patch Available)
I committed this to the HADOOP-13345 feature branch. [~liuml07], thank you for
the patch.
> S3Guard: Existing tables may not be initialized correctly in
> DynamoDBMetadataStore
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-13908
> URL: https://issues.apache.org/jira/browse/HADOOP-13908
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Mingliang Liu
> Assignee: Mingliang Liu
> Fix For: HADOOP-13345
>
> Attachments: HADOOP-13908-HADOOP-13345.000.patch,
> HADOOP-13908-HADOOP-13345.001.patch, HADOOP-13908-HADOOP-13345.002.patch,
> HADOOP-13908-HADOOP-13345.002.patch, HADOOP-13908-HADOOP-13345.003.patch,
> HADOOP-13908-HADOOP-13345.004.patch, HADOOP-13908-HADOOP-13345.005.patch,
> HADOOP-13908-HADOOP-13345.006.patch
>
>
> This was based on discussion in [HADOOP-13455]. Though we should not create
> table unless the config {{fs.s3a.s3guard.ddb.table.create}} is set true, we
> still have to get the existing table in
> {{DynamoDBMetadataStore#initialize()}} and wait for its becoming active,
> before any table/item operations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
