You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Mingliang Liu (JIRA)" <ji...@apache.org> on 2017/01/05 01:16:58 UTC
[jira] [Comment Edited] (HADOOP-13908) S3Guard: Existing tables may
not be initialized correctly in DynamoDBMetadataStore
[ https://issues.apache.org/jira/browse/HADOOP-13908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799289#comment-15799289 ]
Mingliang Liu edited comment on HADOOP-13908 at 1/5/17 1:16 AM:
----------------------------------------------------------------
For the 2nd comment, yes v4 patch follows this pattern: if get() succeeds, we'll simply return.
was (Author: liuml07):
For the 2nd comment, yes v4 patch follows this pattern.
> 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
> 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
>
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org