[
https://issues.apache.org/jira/browse/HIVE-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031434#comment-14031434
]
Thejas M Nair commented on HIVE-7224:
-------------------------------------
[~vgumashta] It looks like the way the column sizes are estimated is different
in case of incremental and buffered mode. In case of incremental mode, it seems
to look at the ResultSetMetadata.getColumnDisplaySize to estimate how much
width is to be given for each column. Can you check how different the
formatting is with these two modes ?
> Set incremental printing to true by default in Beeline
> ------------------------------------------------------
>
> Key: HIVE-7224
> URL: https://issues.apache.org/jira/browse/HIVE-7224
> Project: Hive
> Issue Type: Bug
> Components: Clients, JDBC
> Affects Versions: 0.13.0
> Reporter: Vaibhav Gumashta
> Assignee: Vaibhav Gumashta
> Fix For: 0.14.0
>
> Attachments: HIVE-7224.1.patch
>
>
> See HIVE-7221.
> By default beeline tries to buffer the entire output relation before printing
> it on stdout. This can cause OOM when the output relation is large. However,
> beeline has the option of incremental prints. We should keep that as the
> default.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
