Fix two small issues #825
Merged
Fix two small issues #825
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
beckettsean
reviewed
Oct 26, 2016
| falls outside the valid time range for InfluxDB. | ||
|
|
||
| The minimum valid timestamp is `-9223372036854775806` or `1677-09-21T00:12:43.145224194Z`. | ||
| The maximum valid timestamp is `9223372036854775806` or `2262-04-11T23:47:16.854775806Z`. |
There was a problem hiding this comment.
According to https://golang.org/pkg/math/, in Go MaxInt64 is 1<<63 - 1, which according to wolfram alpha is 9223372036854775807.
Min is correct, since it's the actual Golang MinInt64 + 2.
There was a problem hiding this comment.
I think the max is 9223372036854775807 - 1. I got the max from https://github.com/influxdata/influxdb/blob/07071279dc550ce7ed7fbd151b7d7385d00ee4c2/models/time.go#L12.
There was a problem hiding this comment.
Okay, it does look like the max you have is correct.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a question to the FAQ about the min and max allowable timestamps in the database. Also adds this information to the line protocol pages and documents the error that occurs when those timestamps are exceeded. Fixes #467.
Adds the
max series per database exceedederror to the errors page. Fixes #819.@beckettsean, I didn't see the
write failed for shard XXtext in themax series per database exceedederror. I tested it out on OSS 1.0.2.