You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Sergio Peña (JIRA)" <ji...@apache.org> on 2016/08/30 15:36:21 UTC
[jira] [Updated] (HIVE-14170) Beeline IncrementalRows should buffer
rows and incrementally re-calculate width if TableOutputFormat is used
[ https://issues.apache.org/jira/browse/HIVE-14170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergio Peña updated HIVE-14170:
-------------------------------
Resolution: Fixed
Fix Version/s: 2.2.0
Status: Resolved (was: Patch Available)
Thanks [~stakiar]. I committed this to master.
> Beeline IncrementalRows should buffer rows and incrementally re-calculate width if TableOutputFormat is used
> ------------------------------------------------------------------------------------------------------------
>
> Key: HIVE-14170
> URL: https://issues.apache.org/jira/browse/HIVE-14170
> Project: Hive
> Issue Type: Sub-task
> Components: Beeline
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Fix For: 2.2.0
>
> Attachments: HIVE-14170.1.patch, HIVE-14170.2.patch, HIVE-14170.3.patch, HIVE-14170.4.patch
>
>
> If {{--incremental}} is specified in Beeline, rows are meant to be printed out immediately. However, if {{TableOutputFormat}} is used with this option the formatting can look really off.
> The reason is that {{IncrementalRows}} does not do a global calculation of the optimal width size for {{TableOutputFormat}} (it can't because it only sees one row at a time). The output of {{BufferedRows}} looks much better because it can do this global calculation.
> If {{--incremental}} is used, and {{TableOutputFormat}} is used, the width should be re-calculated every "x" rows ("x" can be configurable and by default it can be 1000).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)