Return-Path: X-Original-To: apmail-drill-dev-archive@www.apache.org Delivered-To: apmail-drill-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD6C4194FF for ; Thu, 24 Mar 2016 15:39:26 +0000 (UTC) Received: (qmail 18294 invoked by uid 500); 24 Mar 2016 15:39:26 -0000 Delivered-To: apmail-drill-dev-archive@drill.apache.org Received: (qmail 18018 invoked by uid 500); 24 Mar 2016 15:39:26 -0000 Mailing-List: contact dev-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list dev@drill.apache.org Received: (qmail 17797 invoked by uid 99); 24 Mar 2016 15:39:26 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Mar 2016 15:39:26 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A14D42C1F6A for ; Thu, 24 Mar 2016 15:39:25 +0000 (UTC) Date: Thu, 24 Mar 2016 15:39:25 +0000 (UTC) From: "Chris Matta (JIRA)" To: dev@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DRILL-4533) Error should be more informative when creating/updating storage plugin definition MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Chris Matta created DRILL-4533: ---------------------------------- Summary: Error should be more informative when creating/updating storage plugin definition Key: DRILL-4533 URL: https://issues.apache.org/jira/browse/DRILL-4533 Project: Apache Drill Issue Type: Improvement Components: Storage - Information Schema Reporter: Chris Matta Priority: Minor When updating or creating the definition of a storage plugin fails the error {code}error (unable to create/ update storage)"{code} isn't descriptive enough. It should provide a hint of what's actually wrong: * Is the JSON invalid? If so maybe a hint to where the linter encountered the problem * Unexpected Field? * Deeper issues could maybe include the stack trace? -- This message was sent by Atlassian JIRA (v6.3.4#6332)