diff options
| author | Ilya Matiach <ilmat@microsoft.com> | 2017-01-24 10:25:12 -0800 |
|---|---|---|
| committer | Joseph K. Bradley <joseph@databricks.com> | 2017-01-24 10:25:12 -0800 |
| commit | d9783380ff0a6440117348dee3205826d0f9687e (patch) | |
| tree | cee3600462a2955cdb957bb18663c6672de41a92 /resource-managers | |
| parent | 59c184e028d79286ef490a448ae7f2536d8753d6 (diff) | |
| download | spark-d9783380ff0a6440117348dee3205826d0f9687e.tar.gz spark-d9783380ff0a6440117348dee3205826d0f9687e.tar.bz2 spark-d9783380ff0a6440117348dee3205826d0f9687e.zip | |
[SPARK-18036][ML][MLLIB] Fixing decision trees handling edge cases
## What changes were proposed in this pull request?
Decision trees/GBT/RF do not handle edge cases such as constant features or empty features.
In the case of constant features we choose any arbitrary split instead of failing with a cryptic error message.
In the case of empty features we fail with a better error message stating:
DecisionTree requires number of features > 0, but was given an empty features vector
Instead of the cryptic error message:
java.lang.UnsupportedOperationException: empty.max
## How was this patch tested?
Unit tests are added in the patch for:
DecisionTreeRegressor
GBTRegressor
Random Forest Regressor
Author: Ilya Matiach <ilmat@microsoft.com>
Closes #16377 from imatiach-msft/ilmat/fix-decision-tree.
Diffstat (limited to 'resource-managers')
0 files changed, 0 insertions, 0 deletions