You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: This should trigger any time that the set of columns is different. If the set is the same -- but the columns are just in a different order -- then we should proceed with the transformation.
Scenario 3: User tries to fit a dataset that does not have the same columns as the config
Note: This should trigger any time that the set of columns is different. If the set is the same -- but the columns are just in a different order -- then we should proceed with the fit.
The text was updated successfully, but these errors were encountered:
Expected behavior
We should check input and provide friendly tips, warnings and errors to guide the user into correct
HyperTransformer
usage.Scenario 1: User calls
fit
orfit_transform
directly without using the newauto_detect_config
method (see #399)Scenario 2: User tries to transform a dataset that does not have the same column names or sdtypes as the fit data.
Note: This should trigger any time that the set of columns is different. If the set is the same -- but the columns are just in a different order -- then we should proceed with the transformation.
Scenario 3: User tries to fit a dataset that does not have the same columns as the config
Note: This should trigger any time that the set of columns is different. If the set is the same -- but the columns are just in a different order -- then we should proceed with the fit.
The text was updated successfully, but these errors were encountered: