Github user WeichenXu123 commented on the issue:
https://github.com/apache/spark/pull/20164
@srowen yeah, all models exist this issue. Although, a little difference,
for other models, it is very straightforward for user to call
`setRawPrediction` to avoid overwrite the same name column. But for OVSModel,
it is a little tricky (user have to call the wrapped classification model 's
`setRawPrediction` method), user is hard to aware the root cause why existing
column be overwritten. So change it to use temporary column name seems to be a
better way.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
