From common-issues-return-148674-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Thu Feb 22 11:36:07 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1B3E718067E for ; Thu, 22 Feb 2018 11:36:06 +0100 (CET) Received: (qmail 80746 invoked by uid 500); 22 Feb 2018 10:36:06 -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 80734 invoked by uid 99); 22 Feb 2018 10:36:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Feb 2018 10:36:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 76D0F180033 for ; Thu, 22 Feb 2018 10:36:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ckHWcv4ItUUT for ; Thu, 22 Feb 2018 10:36:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 6D5CD5F1B3 for ; Thu, 22 Feb 2018 10:36:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id E1ADDE01AE for ; Thu, 22 Feb 2018 10:36:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 83C08262E8 for ; Thu, 22 Feb 2018 10:36:02 +0000 (UTC) Date: Thu, 22 Feb 2018 10:36:02 +0000 (UTC) From: "Steve Loughran (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-15193) add bulk delete call to metastore API & DDB impl MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-15193?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 372638#comment-16372638 ]=20 Steve Loughran commented on HADOOP-15193: ----------------------------------------- I'm thinking of doing this with some explicit {{BulkOperationInfo extends C= loseable}} class and {code} BulkOperationInfo initiateDirectoryDelete(path) void deleteBatch(BulkOperationInfo, List) // every path must be under= the path specified in the bulk operation void completeBulkOperation(BulkOperationInfo, boolean wasSuccessful)=20 {code} This lines us up for setting up other bulk ops, like an explicit rename. Why this way? It allows us to tell the store that the batches are all part = of the same rmdir call, and that there is little/no need to create any pare= nt dir markers, etc, etc, because everything is expected to work. The compl= ete call can do that and choose what to use as a success/failure marker. The base impl will do nothing but very that in a batch delete, all paths ar= e valid, then issue 1 by 1; nothing done in complete() > add bulk delete call to metastore API & DDB impl > ------------------------------------------------ > > Key: HADOOP-15193 > URL: https://issues.apache.org/jira/browse/HADOOP-15193 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 3.0.0 > Reporter: Steve Loughran > Priority: Major > > recursive dir delete (and any future bulk delete API like=C2=A0HADOOP-151= 91) benefits from using the DDB bulk table delete call, which takes a list = of deletes and executes. Hopefully this will offer better perf.=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org