You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Eren Avsarogullari (Jira)" <ji...@apache.org> on 2020/04/13 20:09:00 UTC
[jira] [Updated] (SPARK-31440) Improve SQL Rest API
[ https://issues.apache.org/jira/browse/SPARK-31440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eren Avsarogullari updated SPARK-31440:
---------------------------------------
Description:
SQL Rest API exposes query execution metrics as Public API. This Jira aims to apply following improvements on SQL Rest API by aligning Spark-UI.
*Proposed Improvements:*
1- Support Physical Operations and group metrics per operation by aligning Spark UI.
2- *nodeId* can be useful for grouping metrics as well as for sorting and to differentiate same operators and their metrics.
3- Filter *blank* metrics by aligning with Spark UI - SQL Tab
4- Remove *\n* from *metricValue(s)*
5- *planDescription* can be optional Http parameter to avoid network cost (specially for complex jobs creating big-plans).
6- *metrics* attribute needs to be exposed at the bottom order as *metricDetails*. This order matches with Spark UI by highlighting with execution order.
*Attachments:*
Please find both *current* and *improved* versions of results as attached.
was:
SQL Rest API exposes query execution metrics as Public API. This Jira aims to apply following improvements on SQL Rest API by aligning Spark-UI.
*Proposed Improvements:*
1- Support Physical Operations and group metrics per operation by aligning Spark UI.
2- `nodeId` can be useful for grouping metrics as well as for sorting and to differentiate same operators and their metrics.
3- Filter `blank` metrics by aligning with Spark UI - SQL Tab
4- Remove `\n` from `metricValue`
5- `planDescription` can be optional Http parameter to avoid network cost (specially for complex jobs creating big-plans).
6- `metrics` attribute needs to be exposed at the bottom order as `metricDetails`. This order matches with Spark UI by highlighting with execution order.
*Attachments:*
Please find both *current* and *improved* versions of results as attached.
> Improve SQL Rest API
> --------------------
>
> Key: SPARK-31440
> URL: https://issues.apache.org/jira/browse/SPARK-31440
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Eren Avsarogullari
> Priority: Major
>
> SQL Rest API exposes query execution metrics as Public API. This Jira aims to apply following improvements on SQL Rest API by aligning Spark-UI.
> *Proposed Improvements:*
> 1- Support Physical Operations and group metrics per operation by aligning Spark UI.
> 2- *nodeId* can be useful for grouping metrics as well as for sorting and to differentiate same operators and their metrics.
> 3- Filter *blank* metrics by aligning with Spark UI - SQL Tab
> 4- Remove *\n* from *metricValue(s)*
> 5- *planDescription* can be optional Http parameter to avoid network cost (specially for complex jobs creating big-plans).
> 6- *metrics* attribute needs to be exposed at the bottom order as *metricDetails*. This order matches with Spark UI by highlighting with execution order.
> *Attachments:*
> Please find both *current* and *improved* versions of results as attached.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org