[
https://issues.apache.org/jira/browse/HIVE-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15363295#comment-15363295
]
Sahil Takiar commented on HIVE-7224:
------------------------------------
{quote}
I think it is better to keep the column width to be consistent across all rows
in the output, rather than adjust it every 1000 rows.
{quote}
Thanks for the input [~thejas]! To clarify, what would happen if Beeline uses
the first 1000 rows to calculate the width, but then row 1001th is longer than
that width. In that case the width would have to be widened for that row,
right? I think that is what the current implementation of {{--incremental}} is
doing.
I like the idea of keeping the width the same for all rows, even in incremental
mode, but I'm not sure how it would work. Thoughts?
> 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: Beeline, Clients, JDBC
> Affects Versions: 0.13.0, 1.0.0, 1.2.0, 1.1.0
> Reporter: Vaibhav Gumashta
> Assignee: Sahil Takiar
> Attachments: HIVE-7224.1.patch, HIVE-7224.2.patch, HIVE-7224.2.patch,
> HIVE-7224.3.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.3.4#6332)
