Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Fri, 27 Mar 2015 00:03:54 +0000 (UTC)
From: "Rahul Challapalli (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12786049.1427414583000.44115.1427414634309@Atlassian.JIRA>
In-Reply-To: <JIRA.12786049.1427414583000@Atlassian.JIRA>
References: <JIRA.12786049.1427414583000@Atlassian.JIRA>
 <JIRA.12786049.1427414583729@arcas>
Subject: [jira] [Created] (DRILL-2589) Creating a view with duplicate column
 names should fail or give a warning to the user
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Rahul Challapalli created DRILL-2589:
----------------------------------------

             Summary: Creating a view with duplicate column names should fail or give a warning to the user
                 Key: DRILL-2589
                 URL: https://issues.apache.org/jira/browse/DRILL-2589
             Project: Apache Drill
          Issue Type: Bug
          Components: Metadata
            Reporter: Rahul Challapalli
            Assignee: Steven Phillips


git.commit.id.abbrev=4d398ed

View DDL :
{code}
create view v1 as select pageRank, pageRank  from `/dfs/parquet/rankings`; 
{code}

The above view creation succeeds and drill silently renames the columns. Postgres does not allow this behavior.

Below is the description of the view
{code}
describe v1;
+-------------+------------+-------------+
| COLUMN_NAME | DATA_TYPE  | IS_NULLABLE |
+-------------+------------+-------------+
| pageRank    | ANY        | NO          |
| pageRank0   | ANY        | NO          |
+-------------+------------+-------------+
{code}

In most cases the reason someone would create such a view is by mistake. So we should either not allow it or give a warning to the user in such situations


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)