Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Mon, 4 May 2015 23:46:06 +0000 (UTC)
From: "Rahul Challapalli (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12781898.1426272729000.76366.1430783166035@Atlassian.JIRA>
In-Reply-To: <JIRA.12781898.1426272729000@Atlassian.JIRA>
References: <JIRA.12781898.1426272729000@Atlassian.JIRA>
 <JIRA.12781898.1426272729208@arcas>
Subject: [jira] [Closed] (DRILL-2450) JDBC : DatabaseMetaData.getColumns is
 missing the 'COLUMN_SIZE' in the result set
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DRILL-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rahul Challapalli closed DRILL-2450.
------------------------------------

Verified that we are returning the column size value! However there seems to be a discrepancy between the actual values returned by drill and postgres for certain types. Will raise a separate JIRA for that

> JDBC : DatabaseMetaData.getColumns is missing the 'COLUMN_SIZE' in the result set
> ---------------------------------------------------------------------------------
>
>                 Key: DRILL-2450
>                 URL: https://issues.apache.org/jira/browse/DRILL-2450
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>            Reporter: Rahul Challapalli
>            Assignee: Daniel Barclay (Drill)
>            Priority: Blocker
>             Fix For: 1.1.0
>
>
> git.commit.id.abbrev=e92db23
> DatabaseMetaData.getColumns is missing the 'COLUMN_SIZE' in the result set. This is also screwing up the order in which other fields are returned. 
> Below is the column size returned by postgres for different data types. Though its specific to the data, I am just adding it here
> {code}
> int8 : 19   (this is a bigint column)
> bool:1
> date:13
> float8:17  (this is a double column)
> float8:17 (this is a float column)
> int4 : 10
> time:15
> timestamp : 29
> varchar : 50
> {code}
> Below are few things an analytic tool might use which are currently not working because of this :
> {code}
> DECIMAL_DIGITS : 9
> NULLABLE : 11
> REMARKS : 12
> {code}


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