hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergio Peña (JIRA) <>
Subject [jira] [Commented] (HIVE-14135) beeline output not formatted correctly for large column widths
Date Wed, 13 Jul 2016 23:01:20 GMT


Sergio Peña commented on HIVE-14135:

The patch looks good. Just a couple of questions:

- Is the setUp() method needed? Can we remove it?

- What's the difference between DEFAULT_MAX_COLUMN_WIDTH and DEFAULT_MAX_WIDTH? Why do they
have 80 vs 50?
- Is there a way to specify the max width from a command line parameter?

> 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, HIVE-14135.2.patch, longKeyValues.txt, output_after.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