From 642d8466d67e7eafb448801b7b2604625a3eb8c7 Mon Sep 17 00:00:00 2001 From: Sean Beckett Date: Fri, 27 May 2016 17:57:21 -0600 Subject: [PATCH 1/5] remove old blog post --- content/influxdb/v0.13/concepts/crosswalk.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/content/influxdb/v0.13/concepts/crosswalk.md b/content/influxdb/v0.13/concepts/crosswalk.md index 4005362fbe..66d5b0c635 100644 --- a/content/influxdb/v0.13/concepts/crosswalk.md +++ b/content/influxdb/v0.13/concepts/crosswalk.md @@ -192,6 +192,3 @@ In addition, time series data is generally written once and rarely updated. The result is that InfluxDB is not a full CRUD database but more like a CR-ud, prioritizing the performance of creating and reading data over update and destroy, and preventing some update and destroy behaviors to make create and read more performant. -For more information on why InfluxDB made these architectural decisions [Paul Dix](https://github.com/pauldix) -has an excellent [blog post](https://influxdata.com/blog/influxdb-clustering-design-neither-strictly-cp-or-ap/) -with more explanation. From bd6ca279e9c5ba2310939653a584666b8de1da68 Mon Sep 17 00:00:00 2001 From: Sean Beckett Date: Fri, 27 May 2016 17:57:46 -0600 Subject: [PATCH 2/5] Update insights_tradeoffs.md --- content/influxdb/v0.13/concepts/insights_tradeoffs.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/influxdb/v0.13/concepts/insights_tradeoffs.md b/content/influxdb/v0.13/concepts/insights_tradeoffs.md index 14a9799996..386ef1d723 100644 --- a/content/influxdb/v0.13/concepts/insights_tradeoffs.md +++ b/content/influxdb/v0.13/concepts/insights_tradeoffs.md @@ -40,5 +40,3 @@ there are no cross table joins 1. No one point is too important. * *Pro:* InfluxDB has very powerful tools to deal with aggregate data and large data sets * *Con:* Points don't have IDs in the traditional sense, they are differentiated by timestamp and series - -For more information on this topic please refer to this [blog post](https://influxdata.com/blog/influxdb-clustering-design-neither-strictly-cp-or-ap/) by Paul Dix. From fc8eee9b54004b8d9480d0ce28daf2fdea625171 Mon Sep 17 00:00:00 2001 From: Sean Beckett Date: Fri, 27 May 2016 18:10:14 -0600 Subject: [PATCH 3/5] removing no longer relevant GHI references --- .../v0.13/troubleshooting/frequently_encountered_issues.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/content/influxdb/v0.13/troubleshooting/frequently_encountered_issues.md b/content/influxdb/v0.13/troubleshooting/frequently_encountered_issues.md index 65e74f2321..1152442ef5 100644 --- a/content/influxdb/v0.13/troubleshooting/frequently_encountered_issues.md +++ b/content/influxdb/v0.13/troubleshooting/frequently_encountered_issues.md @@ -132,8 +132,6 @@ See [Go builtins](http://golang.org/pkg/builtin/#int64) for more information. Values close to but within those limits may lead to unexpected results; some functions and operators convert the int64 data type to float64 during calculation which can cause overflow issues. -
[GitHub Issue #3130](https://github.com/influxdb/influxdb/issues/3130)
- ## Doing math on timestamps Currently, it is not possible to execute mathematical operators or functions against timestamp values in InfluxDB. All time calculations must be carried out by the client receiving the query results. @@ -142,8 +140,6 @@ All time calculations must be carried out by the client receiving the query resu In InfluxDB, epoch 0 (`1970-01-01T00:00:00Z`) is often used as a null timestamp equivalent. If you request a query that has no timestamp to return, such as an aggregation function with an unbounded time range, InfluxDB returns epoch 0 as the timestamp. -
[GitHub Issue #3337](https://github.com/influxdb/influxdb/issues/3337)
- ## Getting large query returns in batches when using the HTTP API InfluxDB returns large query results in batches of 10,000 points unless you use the query string parameter `chunk_size` to explicitly set the batch size. For example, get results in batches of 20,000 points with: From 282df7bede68168ac01ec8f783b79b6d01057a03 Mon Sep 17 00:00:00 2001 From: Sean Beckett Date: Fri, 27 May 2016 18:11:38 -0600 Subject: [PATCH 4/5] Update data_exploration.md --- content/influxdb/v0.13/query_language/data_exploration.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/content/influxdb/v0.13/query_language/data_exploration.md b/content/influxdb/v0.13/query_language/data_exploration.md index 213b94e3ff..44ee7e3564 100644 --- a/content/influxdb/v0.13/query_language/data_exploration.md +++ b/content/influxdb/v0.13/query_language/data_exploration.md @@ -649,10 +649,6 @@ InfluxQL supports two different clauses to limit your query results: * `SLIMIT ` returns every point from \ series in the specified measurement. * `LIMIT ` followed by `SLIMIT ` returns the first \ points from \ series in the specified measurement. -
Please note that using `LIMIT` and `SLIMIT` **without** a `GROUP BY *` clause can cause unexpected results. -See [GitHub Issue #4232](https://github.com/influxdb/influxdb/issues/4232) for more information. -
- ### Limit the number of results returned per series with `LIMIT` --- Use `LIMIT ` with `SELECT` and `GROUP BY *` to return the first \ points from each series. From 6bfc60e0415d89d440d11f5362f483fa41638ce4 Mon Sep 17 00:00:00 2001 From: Sean Beckett Date: Fri, 27 May 2016 18:18:26 -0600 Subject: [PATCH 5/5] errors are now returned on out of bounds timestamps --- .../troubleshooting/frequently_encountered_issues.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/content/influxdb/v0.13/troubleshooting/frequently_encountered_issues.md b/content/influxdb/v0.13/troubleshooting/frequently_encountered_issues.md index 1152442ef5..172684379e 100644 --- a/content/influxdb/v0.13/troubleshooting/frequently_encountered_issues.md +++ b/content/influxdb/v0.13/troubleshooting/frequently_encountered_issues.md @@ -14,7 +14,6 @@ Where applicable, it links to outstanding issues on GitHub. * [Understanding the time intervals returned from `GROUP BY time()` queries](/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#understanding-the-time-intervals-returned-from-group-by-time-queries) * [Querying after `now()`](/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#querying-after-now) -* [Querying outside the min/max time range](/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#querying-outside-the-min-max-time-range) * [Querying a time range that spans epoch 0](/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#querying-a-time-range-that-spans-epoch-0) * [Querying with booleans](/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#querying-with-booleans) * [Working with really big or really small integers](/influxdb/v0.13/troubleshooting/frequently_encountered_issues/#working-with-really-big-or-really-small-integers) @@ -96,14 +95,6 @@ The second query asks InfluxDB to return everything from `hillvalley` that occur `SELECT * FROM hillvalley` `SELECT * FROM hillvalley WHERE time < now() + 1000d` -## Querying outside the min/max time range -Queries with a time range that exceeds the minimum or maximum timestamps valid for InfluxDB currently return no results, rather than an error message. - -Smallest valid timestamp: `-9023372036854775808` (approximately `1684-01-22T14:50:02Z`) -Largest valid timestamp: `9023372036854775807` (approximately `2255-12-09T23:13:56Z`) - -
[GitHub Issue #3369](https://github.com/influxdb/influxdb/issues/3369)
- ## Querying a time range that spans epoch 0 Currently, InfluxDB can return results for queries that cover either the time range before epoch 0 or the time range after epoch 0, not both. A query with a time range that spans epoch 0 returns partial results.