Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3D86E10B88 for ; Thu, 20 Nov 2014 19:16:34 +0000 (UTC) Received: (qmail 68633 invoked by uid 500); 20 Nov 2014 19:16:34 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 68588 invoked by uid 500); 20 Nov 2014 19:16:34 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 68569 invoked by uid 99); 20 Nov 2014 19:16:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Nov 2014 19:16:34 +0000 Date: Thu, 20 Nov 2014 19:16:33 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ACCUMULO-3352) Confusing BulkImport error message MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Christopher Tubbs created ACCUMULO-3352: ------------------------------------------- Summary: Confusing BulkImport error message Key: ACCUMULO-3352 URL: https://issues.apache.org/jira/browse/ACCUMULO-3352 Project: Accumulo Issue Type: Bug Components: fate Affects Versions: 1.6.1 Reporter: Christopher Tubbs Fix For: 1.6.2, 1.7.0 BulkImport fails with a confusing message when it tries to create a temporary bulk import directory: {{__ is not in a known namespace}} This is very confusing, because it refers to volumes as "namespace" (an early working term for volumes), and it does not clearly explain the constraint that bulk imported files must exist in a volume that is configured in Accumulo. Further, as an {{IllegalStateException}}, the error message does not get propagated to the client which initiated the bulk import. Instead, an exception gets thrown indicating an error waiting for a Fate operation. One must examine the Master logs to determine the actual problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)