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

Gregorian vs. Unix timestamps [JIRA: RIAK-2346] #801

Open
lucasbru opened this issue Jan 8, 2016 · 1 comment
Open

Gregorian vs. Unix timestamps [JIRA: RIAK-2346] #801

lucasbru opened this issue Jan 8, 2016 · 1 comment

Comments

@lucasbru
Copy link

lucasbru commented Jan 8, 2016

This might be a non-issue, but I realized that timestamps in vector clocks are defined as of year 0 instead of year 1970, leading to a 5-byte large integer encoding instead of the usual 4-byte encoding. Is that worth the potential performance hit?

@Basho-JIRA Basho-JIRA changed the title Gregorian vs. Unix timestamps Gregorian vs. Unix timestamps [JIRA: RIAK-2346] Jan 8, 2016
@jonmeredith
Copy link
Contributor

The reasons are mostly historical around the calendar module. There's no real need for anything beyond the time the vclock is first created in a cluster.

It's something we'd like to get around to re-engineering, but for Riak we need to worry about compatibility and changing to a more recent epoch will make them smaller and confusing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants