Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upEnforce timestamp monotonicity #481
Comments
beorn7
self-assigned this
Jan 27, 2015
beorn7
added
the
enhancement
label
Feb 2, 2015
beorn7
changed the title
Enforce timestamp monotony
Enforce timestamp monotonicity
Mar 14, 2015
juliusv
referenced this issue
Jul 12, 2015
Merged
Ensure timestamp monotonicity within a series. #889
This comment has been minimized.
This comment has been minimized.
|
When we append a new sample to an archived series, we unarchive the series anyways and get the last timestamp of the series from the unarchiving. So even that case seems to be cheap to check. Implementation: #889 |
juliusv
added a commit
that referenced
this issue
Jul 13, 2015
beorn7
added a commit
that referenced
this issue
Jul 13, 2015
beorn7
added a commit
that referenced
this issue
Jul 15, 2015
beorn7
closed this
in
#889
Jul 16, 2015
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
beorn7 commentedJan 27, 2015
The storage requires that samples are sorted by timestamp, i.e. a timestamp that is saved to the storage layer must have a timestamp at least as high as the previous sample. This constraint is just by contract so far. It is not checked or enforced.
Unfortunately, that's not trivial as a time series might already be archived when a sample for it comes in again. It's pretty expensive to unarchive a series just to check the latest timestamp.
Ideas: