hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thejas M Nair (JIRA)" <>
Subject [jira] [Commented] (HIVE-14135) beeline output not formatted correctly for large column widths
Date Thu, 07 Jul 2016 01:14:10 GMT


Thejas M Nair commented on HIVE-14135:

Thanks [~vihangk1] for the examples.
This change would make BufferedRows give practically the same output as IncrementalRows if
columns are larger than the maxwidth of 15 chars.
Can we also increase the default maxWidth as part of this change, so that in most cases the
formatting is still good. Maybe something like 50 chars ?

Can you also please include an unit test case ?

> beeline output not formatted correctly for large column widths
> --------------------------------------------------------------
>                 Key: HIVE-14135
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Beeline
>    Affects Versions: 2.2.0
>            Reporter: Vihang Karajgaonkar
>            Assignee: Vihang Karajgaonkar
>         Attachments: HIVE-14135.1.patch, longKeyValues.txt, output_after.txt, output_before.txt
> If the column width is too large then beeline uses the maximum column width when normalizing
all the column widths. In order to reproduce the issue, run set -v; 
> Once the configuration variables is classpath which can be extremely large width (41k
characters in my environment).

This message was sent by Atlassian JIRA

View raw message