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 89C8B200C53 for ; Tue, 28 Mar 2017 03:06:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 884B9160B99; Tue, 28 Mar 2017 01:06:08 +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 C5F8F160B85 for ; Tue, 28 Mar 2017 03:06:07 +0200 (CEST) Received: (qmail 67175 invoked by uid 500); 28 Mar 2017 01:06:06 -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 67164 invoked by uid 99); 28 Mar 2017 01:06:06 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Mar 2017 01:06:06 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 62768DFDCD; Tue, 28 Mar 2017 01:06:06 +0000 (UTC) From: jinfengni To: dev@drill.apache.org Reply-To: dev@drill.apache.org References: In-Reply-To: Subject: [GitHub] drill issue #801: DRILL-5378: Put more information for schema change excepti... Content-Type: text/plain Message-Id: <20170328010606.62768DFDCD@git1-us-west.apache.org> Date: Tue, 28 Mar 2017 01:06:06 +0000 (UTC) archived-at: Tue, 28 Mar 2017 01:06:08 -0000 Github user jinfengni commented on the issue: https://github.com/apache/drill/pull/801 Agreed with @paul-rogers 's comment regarding overuse SchemaChangeException in the code. I actually planned to open a jira, if no one has been opened yet. We currently use SchemaChangeException in many situations, including real schema change or operational error for "something is wrong" --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---