[
https://issues.apache.org/jira/browse/HIVE-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364704#comment-15364704
]
Sahil Takiar commented on HIVE-7224:
------------------------------------
Thanks for the explanation [~thejas]!
So if my understanding is correct, one approach would be to:
* Modify the logic so that the width is only calculated if
{{TableOutputFormat}} is used
** This will save CPU cycles when the outputformat = a delimiter separated
value format
* Modify {{IncrementalRows}} so that it re-calculates the width every 1000 rows
** I think the advantage of doing it every 1000 rows is just for human
readability purposes
Does that sound reasonable to you?
> 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)
