[jira] [Updated] (HIVE-19733) RemoteSparkJobStatus#getSparkStageProgress inefficient implementation
[ https://issues.apache.org/jira/browse/HIVE-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Takiar updated HIVE-19733: Resolution: Fixed Fix Version/s: 4.0.0 Status: Resolved (was: Patch Available) Pushed to master. > 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 > Fix For: 4.0.0 > > 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)
[jira] [Updated] (HIVE-19733) RemoteSparkJobStatus#getSparkStageProgress inefficient implementation
[ https://issues.apache.org/jira/browse/HIVE-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharathkrishna Guruvayoor Murali updated HIVE-19733: Attachment: HIVE-19733.3.patch > 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)
[jira] [Updated] (HIVE-19733) RemoteSparkJobStatus#getSparkStageProgress inefficient implementation
[ https://issues.apache.org/jira/browse/HIVE-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharathkrishna Guruvayoor Murali updated HIVE-19733: Attachment: HIVE-19733.2.patch > 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 > > > 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)
[jira] [Updated] (HIVE-19733) RemoteSparkJobStatus#getSparkStageProgress inefficient implementation
[ https://issues.apache.org/jira/browse/HIVE-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharathkrishna Guruvayoor Murali updated HIVE-19733: Status: Patch Available (was: Open) > 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 > > > 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)
[jira] [Updated] (HIVE-19733) RemoteSparkJobStatus#getSparkStageProgress inefficient implementation
[ https://issues.apache.org/jira/browse/HIVE-19733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharathkrishna Guruvayoor Murali updated HIVE-19733: Attachment: HIVE-19733.1.patch > 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 > > > 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)