Skip to content

/ sync

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

Use ms precision for record timestamps in S3 key #54

Merged
merged 1 commit into from Feb 13, 2017
Merged

Use ms precision for record timestamps in S3 key #54

merged 1 commit into from Feb 13, 2017

Conversation

@ayumi
Copy link
Contributor

ayumi commented Feb 13, 2017 •
edited

Fix #53

This uses 3 bytes per S3 key, however with multi-part records we still support up to ~50 KiB per record.
@ayumi
record timestamp in ms precision
Verified
This commit was signed with a verified signature.
ayumi ａｙｕｍｉ  ｙｕ
GPG key ID: FFC29CB6ED2EC961 Learn about signing commits
Loading status checks…
af88453 
Fix #53
@ayumi ayumi requested a review from diracdeltas Feb 13, 2017
@diracdeltas
diracdeltas approved these changes Feb 13, 2017
View changes
@diracdeltas diracdeltas merged commit 723674d into staging Feb 13, 2017
2 checks passed
2 checks passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@diracdeltas diracdeltas deleted the fix/timestamp-ms branch Feb 13, 2017
@ayumi ayumi mentioned this pull request Feb 14, 2017
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@diracdeltas diracdeltas

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
@ayumi @diracdeltas
You can’t perform that action at this time.