Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6595#issuecomment-108124362
As long as this is aimed at 1.4.1 (not 1.4.0), should we design a better
fix? My suggestion would be to have PipelineStage include a Param specifying
whether to use it during transform(). Stages could be used in transform() by
default, but certain Transformers could override the default to skip during
transform(). PipelineModel could read the Param and handle each stage
accordingly.
If that's too big a change for 1.4.1, then this temp fix seems tolerable.
Note: We should document the behavior in the docs.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
