You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Parth Chandra (JIRA)" <ji...@apache.org> on 2015/03/24 21:41:53 UTC
[jira] [Updated] (DRILL-2450) JDBC : DatabaseMetaData.getColumns is
missing the 'COLUMN_SIZE' in the result set
[ https://issues.apache.org/jira/browse/DRILL-2450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Parth Chandra updated DRILL-2450:
---------------------------------
Fix Version/s: 1.1.0
> 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)