Hi Maciej,
Absolutely. We had to copy HasInputCol/s, HasOutputCol/s (along with a
couple of others like HasProbabilityCol) to our repo. Which for most
use-cases is good enough, but for some (e.g. operating on any Transformer
that accepts either our or Sparks HasInputCol) makes the code clunky.
Spark ML Pipelines API (not just Transformers, Estimators and custom
Pipelines classes as well) are definitely not just machine-learning
specific.
We use them heavily in our developement. We're building machine learning
pipelines *BUT* many steps involve joining, schema manipulation,
