drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Khurram Faraaz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-3908) ResultSetMetadata.getColumnDisplaySize() does not return correct column length value
Date Thu, 08 Oct 2015 07:02:26 GMT

    [ https://issues.apache.org/jira/browse/DRILL-3908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948181#comment-14948181
] 

Khurram Faraaz commented on DRILL-3908:
---------------------------------------

I tried that test on Drill 1.2 and I can reproduce it on git.commit.id=eafe0a245a0d4c0234bfbead10c6b2d7c8ef413d

{code}

                // col9 in the SQL query is of varchar type and its width is greater than
10.

                Statement stmt = conn.createStatement();
                String query = "select col9 from FEWRWSPQQ_101";
                ResultSet rs = stmt.executeQuery(query);
                ResultSetMetaData rsmd = rs.getMetaData();

                System.out.println("ResultSetMetadata.getColumnDisplaySize(1) :"+rsmd.getColumnDisplaySize(1));

Output :

ResultSetMetadata.getColumnDisplaySize(1) :10

{code}

> ResultSetMetadata.getColumnDisplaySize() does not return correct column length value
> ------------------------------------------------------------------------------------
>
>                 Key: DRILL-3908
>                 URL: https://issues.apache.org/jira/browse/DRILL-3908
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>    Affects Versions: 1.1.0
>         Environment: Linux lnxx64r6 2.6.32-131.0.15.el6.x86_64 #1 SMP Tue May 10 15:42:40
EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Sergio Lob
>            Priority: Critical
>             Fix For: 1.3.0
>
>
> ResultSetMetadata.getColumnDisplaySize() does not return correct column length value.
In fact, invocation of this method seems to always return value 10.  This causes our JDBC
application to process data incorrectly.  I see that this problem was referenced in jira DRILL-3151,
but the this bug has apparently not been addressed, although status of DRILL-3151 is "resolved".
This is a critical bug for us. 



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

Mime
View raw message