I am importing a model from h2o flow
into h2o steam
and deploying it as a prediction service. A problem that I am having is that the model has a date input feature that was converted to a time
type field when loading the training data .csv for the model in h2o flow
.
These time values are converted to (I think) POSIX timestamps (in milliseconds) in the parsed .hex file in h2o flow
.
Thus, when I deploy models trained on this data in steam
's prediction service, the input fields expect Double
values (the timestamps) rather than any kind of date string (eg. "2016-12-21") which human users of this service are expecting to be able to enter. This is the error that the steam
prediction service gives me for input date 2016-12-21.
Is there any way around this? The service needs to be used by humans and having to have users enter POSIX millisecond timestamps conversions of actual dates makes it unusable. Currently just using a model that does not include date inputs.