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 use of only timestamp or value compression #3

Open
burmanm opened this issue Aug 25, 2016 · 1 comment
Open

Support use of only timestamp or value compression #3

burmanm opened this issue Aug 25, 2016 · 1 comment

Comments

@burmanm
Copy link
Owner

burmanm commented Aug 25, 2016

In some cases, the use of only timestamp or only the value compression is preferred. One of these cases could be the use of high precision in timestamps, where this compression method is not at its best.

Make nextTimestamp() and nextValue() public and allow the use of them directly.
@burmanm
Copy link
Owner Author

burmanm commented Sep 11, 2017

Using only ValueCompression is possible from commit 077ddc8

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
@burmanm