Switch order of boolean checks in infer_feature_types #2661
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
Fixes #2642
I was able to track the regression down to
infer_feature_typeslike @chukarsten and I suspected.Steps to identify problem:
infer_feature_typescorresponding tois_pd_namain
0.30.0
is_pd_nabut the trick is to only do it when the column isUnknown, that's the only case we care about. In python, the booleans are evaluated from left to right so we'll put theis_column_unknowncheck first since that one is near instant. Example:infer_feature_typesnow only takes 10 seconds longer compared to 0.30.0. This is coming from runningconvert_all_nan_unknown_to_doubleand checking if the columns are Unknown.After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of
docs/source/release_notes.rstto include this pull request by adding :pr:123.