Closed
Bug 1356327
Opened 8 years ago
Closed 6 years ago
Use nulls instead of 'unknown' in the churn dataset
Categories
(Data Platform and Tools :: General, enhancement, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: amiyaguchi, Assigned: amiyaguchi)
References
Details
The churn dataset currently uses 'unknown' as a stand in value to nulls. This is useful for CSV values, but probably unnecessary for the parquet dataset.
This should be removed from the parquet churn dataset, and nulls should be filled in the churn_to_csv script.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → amiyaguchi
Points: --- → 2
Priority: -- → P2
Summary: Use nulls instead of 'unknown' in the Churn dataset → Use nulls instead of 'unknown' in the churn dataset
Assignee | ||
Updated•8 years ago
|
Assignee: amiyaguchi → nobody
Updated•7 years ago
|
Assignee: nobody → amiyaguchi
Updated•7 years ago
|
Priority: P2 → P3
Assignee | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Updated•3 years ago
|
Component: Datasets: General → General
You need to log in
before you can comment on or make changes to this bug.
Description
•