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

Support unix timestamps in microseconds (µs) #1889

Open
camsaul opened this issue Feb 5, 2016 · 6 comments

Comments

@camsaul
Copy link
Member

commented Feb 5, 2016

Easy to do and some databases (e.g. BigQuery) use them extensively. I'm sure somebody in the wild stores timestamps this way

@agilliland agilliland added New and removed New labels Feb 5, 2016

@camsaul camsaul self-assigned this Feb 17, 2016

@camsaul camsaul removed their assignment Feb 19, 2016

@salsakran

This comment has been minimized.

Copy link
Contributor

commented Mar 24, 2016

Is this blocked on the new metadata ontology, @agilliland or should we just use the same treatment we have for milliseconds and then collect them all into the new ontology post hoc?

@agilliland

This comment has been minimized.

Copy link
Contributor

commented Mar 25, 2016

Nothing is blocking this technically. My vote would be to wait an see that it's truly needed though since it's a bit obscure to be using microseconds and it adds bloat to the metadata choices if it's never used.

@salsakran

This comment has been minimized.

Copy link
Contributor

commented Mar 25, 2016

Yes. I think this is a good issue to leave open in that it's easy and if anyone actually needs it, it's a 5 line commit.

@Cidan

This comment has been minimized.

Copy link

commented Dec 3, 2016

Hi.

We very, very much need this. We store all of our analytics and user records for 30 million users in microseconds due to the high volume nature of our platform.

You get a vote from me!

@Cidan

This comment has been minimized.

Copy link

commented Apr 18, 2017

Are there any plans on supporting this? It would be of immense use to us.

@chucklessmith

This comment has been minimized.

Copy link

commented Aug 14, 2019

This does appear to be fixed in the current release candidate of 0.33, intentionally or not :) Y'all might be relieved to close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.