This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 30
Use consistent log field names and avoid mixing types #882
Comments
5 tasks
Closed by #883. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For logging, if its the same info, it should have the same field name everywhere. Otherwise it's easy to exclude it from our parquet files accidentally. I have no strong opinion on which name is used in any of these cases, but they need a consistent name.
Here are the ones I've identified thus far:
For mixed types, we use an empty string when no status or logged_status is present which can mess up analysis. We should use a known 'null' value like 0 instead of "" when logging numbers and want to log a lack of one.
The text was updated successfully, but these errors were encountered: