Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6300#issuecomment-121016814
Sorry, I should not have said "map." I agree we should not use map since
that will create an RDD. By map, I really meant UDF.
Here's the sketch of what I meant for transform/predict:
* Predictor.transform: check schema, and call transformImpl
* Predictor.transformImpl: call predict in a UDF, as it does now
* RF/GBT*.predict: keep as is
* RF/GBT*.transformImpl (override): broadcast model, and call UDF. Inside
the UDF, get model from the broadcast variable, and call predict on it.
Does that make sense?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
