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

rfc3339 date limit for time bound queries #6740

Closed
kostasb opened this issue May 27, 2016 · 1 comment
Closed

rfc3339 date limit for time bound queries #6740

kostasb opened this issue May 27, 2016 · 1 comment
Assignees

Comments

@kostasb
Copy link

kostasb commented May 27, 2016

Summary: Time bound queries with rfc3339 are limited to 2050-01-01T00:00:01Z

Tested with both 0.13 and 0.14.0 head 1d467ab

> create database test
> use test
Using database test
> insert ametric,region=1 year=2049 2524607999000000000
> precision rfc3339
> select * from ametric where time <= '2050-01-01T00:00:00Z'
name: ametric
-------------
time            region  year
2049-12-31T23:59:59Z    1   2049

> select * from ametric where time <= '2050-01-01T00:00:01Z'
ERR: time 2050-01-01T00:00:01Z overflows time literal

> precision ns
> select * from ametric where time <= 2524608000000000001
name: ametric
-------------
time            region  year
2524607999000000000 1   2049

The limit seems to be hardcoded int64(2524608000000000000)
https://github.com/influxdata/influxdb/blob/master/influxql/iterator.go

Querying with RFC3339 should support the same time range boundaries as ns precision.

@jsternberg
Copy link
Contributor

The current maximum timestamp was changed to 2262-04-11 23:47:16.854775806 +0000 UTC at some point so I'm going to close this.

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

3 participants