hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-19733) RemoteSparkJobStatus#getSparkStageProgress inefficient implementation
Date Fri, 20 Jul 2018 08:48:00 GMT

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

Hive QA commented on HIVE-19733:
--------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12932290/HIVE-19733.3.patch

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14679 tests passed

Test results: https://builds.apache.org/job/PreCommit-HIVE-Build/12724/testReport
Console output: https://builds.apache.org/job/PreCommit-HIVE-Build/12724/console
Test logs: http://104.198.109.242/logs/PreCommit-HIVE-Build-12724/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12932290 - PreCommit-HIVE-Build

> RemoteSparkJobStatus#getSparkStageProgress inefficient implementation
> ---------------------------------------------------------------------
>
>                 Key: HIVE-19733
>                 URL: https://issues.apache.org/jira/browse/HIVE-19733
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Sahil Takiar
>            Assignee: Bharathkrishna Guruvayoor Murali
>            Priority: Major
>         Attachments: HIVE-19733.1.patch, HIVE-19733.2.patch, HIVE-19733.3.patch
>
>
> The implementation of {{RemoteSparkJobStatus#getSparkStageProgress}} is a bit inefficient.
There is one RPC call to get the {{SparkJobInfo}} and then for every stage there is another
RPC call to get each {{SparkStageInfo}}. This could all be done in a single RPC call.



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

Mime
View raw message