Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API support for type override #99

Closed
dorisjlee opened this issue Sep 27, 2020 · 2 comments
Closed

API support for type override #99

dorisjlee opened this issue Sep 27, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request priority high priority tasks (for dev)

Comments

@dorisjlee
Copy link
Member

Occasionally, there might be mistakes in the data type that is automatically detected in Lux, we should support the ability to let users override the inferred data type and persist this inferred setting throughout the session (even if the metadata has to be recomputed again).

@dorisjlee dorisjlee added enhancement New feature or request priority high priority tasks (for dev) labels Sep 27, 2020
@dorisjlee
Copy link
Member Author

For example, in the real estate data, the Year and Month attributes are detected as temporal, but they are not true datetimes, but a sequence of ordered months and years. User-defined type overriding would be useful here.

df = pd.read_csv("https://github.com/lux-org/lux-datasets/blob/master/data/real_estate_tutorial.csv?raw=true")
# df["Year"] = pd.to_datetime(df["Year"], format='%Y') 
# df["Month"] = pd.to_datetime(df["Month"], format='%M')

@dorisjlee
Copy link
Member Author

Pending documentation and tutorial on data types before we close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority high priority tasks (for dev)
Projects
None yet
Development

No branches or pull requests

2 participants