Skip to content

fix: keep a single feature name from matching other columns - #1998

Open
goelshobhit wants to merge 1 commit into
evidentlyai:mainfrom
goelshobhit:fix-846-string-datetime-feature
Open

goelshobhit wants to merge 1 commit into
evidentlyai:mainfrom
goelshobhit:fix-846-string-datetime-feature

Conversation

@goelshobhit

Copy link
Copy Markdown

Fixes #846

Summary

ColumnMapping accepts one column name or a list for numerical_features, categorical_features, datetime_features, and text_features. Assigning one name left that value as a plain string:

column_mapping.datetime_features = "prediction_timestamp_utc"

A string assigned to datetime_features was tested with `in`, so the column prediction matched prediction_timestamp_utc and was typed as datetime (evidentlyai#846).

Co-authored-by: Cursor <cursoragent@cursor.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix issue with datetime_features column mapping

1 participant