hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Mackrory (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-14046) Metastore destruction test creates table without version marker
Date Fri, 03 Feb 2017 21:53:52 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-14046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Sean Mackrory updated HADOOP-14046:
    Attachment: HADOOP-14046-HADOOP-13345.001.patch

Just combining the 2 tests into 1. Did indeed solve the problem by not having multiple code
paths for creating the table.

> Metastore destruction test creates table without version marker
> ---------------------------------------------------------------
>                 Key: HADOOP-14046
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14046
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>         Attachments: HADOOP-14046-HADOOP-13345.001.patch
> ITestS3GuardToolDynamoDB.testDestroyDynamoDBMetadataStore fails after HADOOP-13985.
> The gist of that test is that it creates a table directly in DynamoDB then tries to destroy
it through S3Guard CLI tools. Since there's another test that tries to create a table through
S3Guard CLI tools then deletes it directly in DynamoDB, I propose just combing the two, so
S3Guard CLI tools are used for init and destroy, and we only use other tools to check for
all the correct side-effects.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message