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.

Sign up for GitHub

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

Jump to bottom

Support both RFC3339 and UTC unix epoch integers for times everywhere #21

Open
britram opened this issue Nov 9, 2017 · 2 comments
Open

Support both RFC3339 and UTC unix epoch integers for times everywhere #21

britram opened this issue Nov 9, 2017 · 2 comments

Comments

@britram
Copy link
Contributor

britram commented Nov 9, 2017

Using ISO/RFC3339 time format everywhere is nice for visibility, but it's less visible urlencoded and takes up more space on obset files. Change the obset format, raw metadata format, and query string format to use seconds since 1970-01-01T00:00:00Z on the wire.
@britram britram added this to the ECN Data Live milestone Nov 9, 2017
@britram
Copy link
Contributor Author

britram commented Dec 6, 2017

Actually, we should support both formats, since we can easily sense which one is in use.

@britram
Copy link
Contributor Author

britram commented Jan 16, 2018

See ParseTime in casting.go. This is not yet done in obset files; need to do a pass to ensure we're consistent here.

@britram britram modified the milestones: ECN Data Live, v3 Beta Jan 16, 2018
@britram britram modified the milestones: v3 Beta 1, v3 Beta 2 Apr 12, 2018
@britram britram changed the title Change time wire format to UTC unix epoch integers Support both RFC3339 and UTC unix epoch integers for times everywhere Apr 17, 2018
@britram britram modified the milestones: v3 Beta 2, v3 Release May 22, 2018
@britram britram removed this from the v3 Release milestone Jun 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@britram