GitHub PushEvent at 2014-08-02 00:10:14
Repository: spark
Actor: dbtsai
Payload: {"shas":[["7058a5393bccc2f917189fa9b4cf7f314410b0de","ccc28e1d2688500738a5d694f8878c48d00e005a@gmail.com","[SPARK-2796] [mllib] DecisionTree bug fix: ordered categorical features\n\nBug: In DecisionTree, the method sequentialBinSearchForOrderedCategoricalFeatureInClassification() indexed bins from 0 to (math.pow(2, featureCategories.toInt - 1) - 1). This upper bound is the bound for unordered categorical features, not ordered ones. The upper bound should be the arity (i.e., max value) of the feature.\n\nAdded new test to DecisionTreeSuite to catch this: \"regression stump with categorical variables of arity 2\"\n\nBug fix: Modified upper bound discussed above.\n\nAlso: Small improvements to coding style in DecisionTree.\n\nCC mengxr manishamde\n\nAuthor: Joseph K. Bradley <joseph.kurata.bradley@gmail.com>\n\nCloses #1720 from jkbradley/decisiontree-bugfix2 and squashes the following commits:\n\n225822f [Joseph K. Bradley] Bug: In DecisionTree, the method sequentialBinSearchForOrderedCategoricalFeatureInClassification() indexed bins from 0 to (math.pow(2, featureCategories.toInt - 1) - 1). This upper bound is the bound for unordered categorical features, not ordered ones. The upper bound should be the arity (i.e., max value) of the feature.","Joseph K. Bradley",true]],"size":1,"ref":"refs/heads/master","head":"7058a5393bccc2f917189fa9b4cf7f314410b0de"}