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 2016/12/21 09:15:58 UTC
[jira] [Assigned] (HADOOP-13925) S3Guard: NPE when table is already
populated in dynamodb and user specifies
"fs.s3a.s3guard.ddb.table.create=false"
[ https://issues.apache.org/jira/browse/HADOOP-13925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mingliang Liu reassigned HADOOP-13925:
--------------------------------------
Assignee: Mingliang Liu
> S3Guard: NPE when table is already populated in dynamodb and user specifies "fs.s3a.s3guard.ddb.table.create=false"
> -------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-13925
> URL: https://issues.apache.org/jira/browse/HADOOP-13925
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Reporter: Rajesh Balamohan
> Assignee: Mingliang Liu
> Priority: Minor
>
> When table is present dynamodb store and already populated, it is possible that users can specify {{fs.s3a.s3guard.ddb.table.create=false}}. In such cases, {{DynamoDBMetadataStore.get}} would end up throwing NPE as {{table}} object may not be initialized.
--
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