You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Bharathkrishna Guruvayoor Murali (JIRA)" <ji...@apache.org> on 2018/05/18 03:47:00 UTC

[jira] [Commented] (HIVE-19602) Refactor inplace progress code in Hive-on-spark progress monitor to use ProgressMonitor

    [ https://issues.apache.org/jira/browse/HIVE-19602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480102#comment-16480102 ] 

Bharathkrishna Guruvayoor Murali commented on HIVE-19602:
---------------------------------------------------------

Idea is to create a ProgressMonitor instance in SparkJobMonitor#printStatusInPlace and display it using InplaceUpdate#render.

This would help in HIVE-19176 as here we need to pass an instance of ProgressMonitor in the response to beeline, so we can maintain uniform format in both cases.

[~stakiar] can you validate if this is a reasonable change.

> Refactor inplace progress code in Hive-on-spark progress monitor to use ProgressMonitor
> ---------------------------------------------------------------------------------------
>
>                 Key: HIVE-19602
>                 URL: https://issues.apache.org/jira/browse/HIVE-19602
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Bharathkrishna Guruvayoor Murali
>            Assignee: Bharathkrishna Guruvayoor Murali
>            Priority: Major
>
> We can refactor the HOS inplace progress monitor code to use InplaceUpdate#render.
> This would be similar to :
> [https://github.com/apache/hive/blob/0b6bea89f74b607299ad944b37e4b62c711aaa69/ql/src/java/org/apache/hadoop/hive/ql/exec/tez/monitoring/RenderStrategy.java#L181]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)