phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Warshavsky (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1759) PhoenixArray to have decent .toString() implementation.
Date Thu, 23 Apr 2015 04:12:38 GMT

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

Alex Warshavsky commented on PHOENIX-1759:
------------------------------------------

Will do, [~ndimiduk]

> PhoenixArray to have decent .toString() implementation.
> -------------------------------------------------------
>
>                 Key: PHOENIX-1759
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1759
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Serhiy Bilousov
>            Assignee: Alex Warshavsky
>            Priority: Minor
>              Labels: Newbie
>             Fix For: 5.0.0, 4.4.0
>
>
> In sqlline when query TABLE or VIEW with ARRAY[] datatype it shows long string as value
for the ARRAY[] column:
> {code}
> org.apache.phoenix.schema.types.PhoenixArray$PrimitiveIntPhoenixArray@d338d 
> {code}
> We getting the string like this because sqlline calls ResultSet.getString() on the array
column. 
> Even thou it more of an issue in sqlline than in PHOENIX, as the value that is returned
is a valid JDBC Array, adding a decent toString implementation in PhoenixArray (or each of
its subclasses) would allow user to see  something like \[ 1,2,3,555,666 \] of what we see
now.



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

Mime
View raw message