tree b5034d30219badc97455a9b6a88f3ec164ce0af6
parent a838ae1510a6677ac3c2ca21a4950d32c5715b4c
author Sanha Lee <sanhaleehana@gmail.com> 1548050708 +0900
committer John Yang <johnyangk@gmail.com> 1548050708 +0900

[NEMO-321] Fix the data skew pass metric mismatch (#188)

JIRA: [NEMO-321: Fix the data skew pass metric mismatch](https://issues.apache.org/jira/projects/NEMO/issues/NEMO-321)

**Major changes:**
- Makes `DataSkewRuntimePass` access to the partitioning logic by moving `Partitioner` interface and the implementations from runtime executor to runtime common.
  - The mismatch between the data metric produced by `MetricCollectionVertex` and the data metric understood by `DataSkewRuntimePass` is caused by the fact that the partitioning logic is hidden from both components.

**Minor changes to note:**
- Adds an empty edge from every metric aggregation vertex to the next stage (as a control dependency) to delay the next stage's scheduling. At now, the order of these stages' scheduling depends on luck.
- Fix the location of `MetricCollection` property.
- Remove the `DynamicOptimization` property (not needed).
- Re-enable the skewness aware scheduling.

**Tests for the changes:**
- Existing integration test and unit tests.

**Other comments:**
- N/A.

Closes #188