From common-issues-return-207752-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org Thu Oct 1 17:46:51 2020 Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@locus.apache.org Delivered-To: apmail-hadoop-common-issues-archive@locus.apache.org Received: from mailroute1-lw-us.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by minotaur.apache.org (Postfix) with ESMTP id 53A941AD3A for ; Thu, 1 Oct 2020 17:46:50 +0000 (UTC) Received: from mail.apache.org (localhost [127.0.0.1]) by mailroute1-lw-us.apache.org (ASF Mail Server at mailroute1-lw-us.apache.org) with SMTP id 0C3491237E8 for ; Thu, 1 Oct 2020 17:46:50 +0000 (UTC) Received: (qmail 40429 invoked by uid 500); 1 Oct 2020 17:46:49 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 40401 invoked by uid 500); 1 Oct 2020 17:46:49 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 40389 invoked by uid 99); 1 Oct 2020 17:46:49 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2020 17:46:49 +0000 From: =?utf-8?q?GitBox?= To: common-issues@hadoop.apache.org Subject: =?utf-8?q?=5BGitHub=5D_=5Bhadoop=5D_smengcl_edited_a_comment_on_pull_request?= =?utf-8?q?_=232352=3A_HDFS-15607=2E_Create_trash_dir_when_allowing_snapshot?= =?utf-8?q?table_dir?= Message-ID: <160157440934.32230.12208109129205928998.asfpy@gitbox.apache.org> Date: Thu, 01 Oct 2020 17:46:49 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit In-Reply-To: References: smengcl edited a comment on pull request #2352: URL: https://github.com/apache/hadoop/pull/2352#issuecomment-701586546 > Do we need to add provisionTrash command for WebHdfs as well? Good point. I think so, yes. Update: As I was attempting to add `PROVISIONSNAPSHOTTRASH` to WebHDFS, I realized `NamenodeWebHdfsMethods` is already server code. But the whole provision trash logic are on the **client** side (same as provision EZ trash). This would also imply that WebHDFS `ALLOWSNAPSHOT` won't trigger provision snapshot trash at the moment. Note WebHDFS doesn't support encryption zone commands (create, list, etc.). I have opened another jira [HDFS-15612](https://issues.apache.org/jira/browse/HDFS-15612) for discussion on WebHDFS support for provision snapshot trash. Let's rule WebHDFS out in this jira for now. @bshashikant ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org