-
- Downloads
[SPARK-20391][CORE] Rename memory related fields in ExecutorSummay
## What changes were proposed in this pull request? This is a follow-up of #14617 to make the name of memory related fields more meaningful. Here for the backward compatibility, I didn't change `maxMemory` and `memoryUsed` fields. ## How was this patch tested? Existing UT and local verification. CC squito and tgravescs . Author: jerryshao <sshao@hortonworks.com> Closes #17700 from jerryshao/SPARK-20391.
Showing
- core/src/main/resources/org/apache/spark/ui/static/executorspage.js 26 additions, 22 deletions...ain/resources/org/apache/spark/ui/static/executorspage.js
- core/src/main/scala/org/apache/spark/status/api/v1/api.scala 7 additions, 4 deletionscore/src/main/scala/org/apache/spark/status/api/v1/api.scala
- core/src/main/scala/org/apache/spark/ui/exec/ExecutorsPage.scala 12 additions, 9 deletions...c/main/scala/org/apache/spark/ui/exec/ExecutorsPage.scala
- core/src/test/resources/HistoryServerExpectations/executor_memory_usage_expectation.json 30 additions, 21 deletions...ServerExpectations/executor_memory_usage_expectation.json
- core/src/test/resources/HistoryServerExpectations/executor_node_blacklisting_expectation.json 30 additions, 21 deletions...rExpectations/executor_node_blacklisting_expectation.json
Loading
Please register or sign in to comment