Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/772#issuecomment-115198124
Actually I wouldn't call it predictSomething, because then we're again
quite close to the former problem that we have a method whose semantics depend
on the provided type. And this only confuses users.
My concern is that the user does not really know what `predictLabeled`
means. Apparently it is something similar to `predict` but with a label. But
what is the label? Does it mean that I can apply `predict` on `T <: Vector` and
`predictLabeled` on `LabeledVector`? Does it mean that I get a labeled result
type? But don't I already get it with `predict`? Do I have to provide a type
with a label or can I also supply a vector?
IMO, the prediction which also returns the true label value deserves a more
distinguishable name than `predictSomething`, because it has different
semantics. I can't think of something better than `evaluate` at the moment. But
it makes it clear that the user has to provide some evaluation `DataSet`,
meaning some labeled data.
---
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.
---
