How should we handle non-feature / non-target columns for PipeOps that generate new samples #825
Labels
Status: Needs Discussion
We still need to think about what the solution should look like
E.g. supersampling, smote etc. -- currently the best we do is throw an error? The more widely used things like weights should probably be supported.
The text was updated successfully, but these errors were encountered: