Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id F1401200C56 for ; Fri, 14 Apr 2017 20:28:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id EFC6F160B8C; Fri, 14 Apr 2017 18:28:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 44BD5160B8A for ; Fri, 14 Apr 2017 20:28:46 +0200 (CEST) Received: (qmail 72422 invoked by uid 500); 14 Apr 2017 18:28:45 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 72411 invoked by uid 99); 14 Apr 2017 18:28:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Apr 2017 18:28:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 11B7AC0254 for ; Fri, 14 Apr 2017 18:28:45 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id RIQRuO0PBVkD for ; Fri, 14 Apr 2017 18:28:44 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AAB265FB49 for ; Fri, 14 Apr 2017 18:28:43 +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 A60AAE0BDC for ; Fri, 14 Apr 2017 18:28:42 +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 C079421B48 for ; Fri, 14 Apr 2017 18:28:41 +0000 (UTC) Date: Fri, 14 Apr 2017 18:28:41 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-17916) Error message not clear when the permission of staging dir is not as expected MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 14 Apr 2017 18:28:47 -0000 [ https://issues.apache.org/jira/browse/HBASE-17916?page=3Dcom.atlassia= n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D159= 69362#comment-15969362 ]=20 Hudson commented on HBASE-17916: -------------------------------- SUCCESS: Integrated in Jenkins build HBase-1.3-JDK7 #143 (See [https://buil= ds.apache.org/job/HBase-1.3-JDK7/143/]) HBASE-17916 Error message not clear when the permission of staging dir (sta= ck: rev e46cbedfa2b86b1649e7229a6aa1d065a4d36cda) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/security/access= /SecureBulkLoadEndpoint.java > Error message not clear when the permission of staging dir is not as expe= cted > -------------------------------------------------------------------------= ---- > > Key: HBASE-17916 > URL: https://issues.apache.org/jira/browse/HBASE-17916 > Project: HBase > Issue Type: Improvement > Components: Operability > Reporter: Xiang Li > Assignee: Xiang Li > Priority: Minor > Labels: easyfix > Fix For: 1.4.0, 1.2.6, 1.3.2 > > Attachments: HBASE-17916.branch-1.000.patch > > > SecureBulkLoadEndpoint checks the permission of staging dir. If it is not= =E2=80=9C-rwx--x--x=E2=80=9D, the following error is prompted: > {code} > Directory already exists but permissions aren't set to '-rwx--x--x' > {code} > It says "Directory", but user has no idea what the directory is. User nee= d to read code according to the stack trace to find that the error is for s= taging dir. > Need to add more info into the error message. > Master branch does not have this issue, as it does not check the permissi= on any more. -- This message was sent by Atlassian JIRA (v6.3.15#6346)