Fix scalar comparison primitives that can fail during feature calculation in some cases #2434
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.
Fixes #2080
Fixes and issue where DFS can create features that cannot be calculated. These features were using the binary comparison to scalar primitives that would attempt to compare a datetime column to a numeric scalar value. This PR removes
Ordinal
andDatetime
input types from the following primitives:LessThanScalar
GreaterThanScalar
LessThanEqualToScalar
GreaterThanEqualToScalar