Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Sun, 11 Nov 2012 00:03:12 +0000 (UTC)
From: "Jing Zhao (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <1195134212.97231.1352592192209.JavaMail.jiratomcat@arcas>
In-Reply-To: <770863199.97229.1352592072933.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (HDFS-4175) Extend existing TestSnapshot to
 support more complicated directory structure and more modifications on
 current files/direcotories
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jing Zhao updated HDFS-4175:
----------------------------

    Attachment: snapshot-test.001.patch

Initial patch. 
                
> Extend existing TestSnapshot to support more complicated directory structure and more modifications on current files/direcotories
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4175
>                 URL: https://issues.apache.org/jira/browse/HDFS-4175
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: data-node, name-node
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>         Attachments: snapshot-test.001.patch
>
>
> Currently the TestSnapshot only uses a static simple directory structure for testing snapshot functionalities. We need to test snapshot under more complicated directory structures. 
> Also the current TestSnapshot only compares snapshots before/after three types of modifications: file creation, deletion, and appending. We need to test snapshots for more file modifications, including file permission change, replication factor change, owner/group change, and sub-directory creation/deletion.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira