-
Notifications
You must be signed in to change notification settings - Fork 7
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
Standardize DateTimes #11
Comments
My vote is for using a |
@tnem I agree on this. It makes it way easier in elastic. But we should also make sure it's something that we can use as elastic's timestamp. |
Any reason not to do both? i.e. epoch and ISO formatted, human readable? ES will store either as epoch internally if the field is mapped as datetime, but it will help folks looking at the json if it's in both. |
@jeffbryner why not... as long as they can both go through json.dumps() and json.loads() I was getting errors with python's straight up "DateTime" type. |
TypeError: datetime.datetime(2017, 3, 6, 19, 13, 16) is not JSON serializable occurs in python for warm_since and warm_for
Let's move them all to same format.
The text was updated successfully, but these errors were encountered: