[
https://issues.apache.org/jira/browse/PHOENIX-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238606#comment-16238606
]
Hadoop QA commented on PHOENIX-2370:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12883280/PHOENIX-2370_v2.patch
against master branch at commit a09cea6bfb94edd95ce06aa2cb7f229227db5666.
ATTACHMENT ID: 12883280
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1617//testReport/
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/1617//console
This message is automatically generated.
> ResultSetMetaData.getColumnDisplaySize() returns bad value for varchar and
> varbinary columns
> --------------------------------------------------------------------------------------------
>
> Key: PHOENIX-2370
> URL: https://issues.apache.org/jira/browse/PHOENIX-2370
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.5.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
> Assignee: Csaba Skrabak
> Priority: Major
> Labels: newbie, verify
> Fix For: 4.14.0
>
> Attachments: PHOENIX-2370.patch, PHOENIX-2370_v2.patch
>
>
> ResultSetMetaData.getColumnDisplaySize() returns bad values for varchar and
> varbinary columns. Specifically, for the following table:
> CREATE TABLE SERGIO (I INTEGER, V10 VARCHAR(10),
> VHUGE VARCHAR(2147483647), V VARCHAR, VB10 VARBINARY(10), VBHUGE
> VARBINARY(2147483647), VB VARBINARY) ;
> 1. getColumnDisplaySize() returns 20 for all varbinary columns, no matter the
> defined size. This should return the max possible size of the column, so:
> getColumnDisplaySize() should return 10 for column VB10,
> getColumnDisplaySize() should return 2147483647 for column VBHUGE,
> getColumnDisplaySize() should return 2147483647 for column VB, assuming that
> a column defined with no size should default to the maximum size.
> 2. getColumnDisplaySize() returns 40 for all varchar columns that are not
> defined with a size, like in column V in the above CREATE TABLE. I would
> think that a VARCHAR column defined with no size parameter should default to
> the maximum size possible, not to a random number like 40.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
