Pipe error messages from XGBoost through to the clients

Description

Let's pipe through the error messages from XGBoost through to the R/Python clients. Right now, there's no information passed on to the client and you have to look through the H2O logs to figure out what went wrong.

I accidentally passed a number outside the allowed range for the colsample_bytree param (must be [0,1]). here’s the error i see in the client (i can’t figure out what went wrong):

In the logs, i can easily debug what the cause is, so it would be nice to pass this to the user:

If I were to do something like this for `h2o.gbm()` then i get a reasonable error in the client:

Activity

Show:
Michal Kurka
February 21, 2021, 6:06 PM

It is not possible to implement as formulated, instead validation checks for sampling rates will be added.

Fixed

Assignee

Michal Kurka

Fix versions

Reporter

Erin LeDell

Support ticket URL

None

Labels

None

Affected Spark version

None

Customer Request Type

None

Task progress

None

ReleaseNotesHidden

None

CustomerVisible

No

Components

Priority

Major