Merge pull request #839 from influxdata/js-show-tag-values-doc
docs(query/influxql): update the transpiler doc for show tag valuespull/10616/head
Jonathan A. Sternberg
GitHub
commit
0e0249ff2e
|
|
@ -4,87 +4,50 @@ The InfluxQL Transpiler exists to rewrite an InfluxQL query into its equivalent
|
|||
|
||||
**NOTE:** The transpiler code is not finished and may not necessarily reflect what is in this document. When they conflict, this document is considered to be the correct way to do it. If you wish to change how the transpiler works, modify this file first.
|
||||
|
||||
1. [Identify the cursors](#identify-cursors)
|
||||
2. [Identify the query type](#identify-query-type)
|
||||
3. [Meta Queries](#meta-queries)
|
||||
1. [SHOW TAG VALUES](#show-tag-values)
|
||||
4. [Data Queries](#data-queries)
|
||||
1. [Group the cursors](#group-cursors)
|
||||
2. [Create the cursors for each group](#create-groups)
|
||||
1. [Create cursor](#create-cursor)
|
||||
2. [Filter by measurement and fields](#filter-cursor)
|
||||
3. [Generate the pivot table](#generate-pivot-table)
|
||||
4. [Evaluate the condition](#evaluate-condition)
|
||||
5. [Perform the grouping](#perform-grouping)
|
||||
6. [Evaluate the function](#evaluate-function)
|
||||
7. [Normalize the time column](#normalize-time)
|
||||
8. [Combine windows](#combine-windows)
|
||||
5. [Join the groups](#join-groups)
|
||||
6. [Map and eval columns](#map-and-eval)
|
||||
5. [Encoding the results](#encoding)
|
||||
1. [Select Statement](#select-statement)
|
||||
1. [Identify the cursors](#identify-cursors)
|
||||
2. [Identify the query type](#identify-query-type)
|
||||
3. [Group the cursors](#group-cursors)
|
||||
4. [Create the cursors for each group](#create-groups)
|
||||
1. [Create cursor](#create-cursor)
|
||||
2. [Filter by measurement and fields](#filter-cursor)
|
||||
3. [Generate the pivot table](#generate-pivot-table)
|
||||
4. [Evaluate the condition](#evaluate-condition)
|
||||
5. [Perform the grouping](#perform-grouping)
|
||||
6. [Evaluate the function](#evaluate-function)
|
||||
7. [Normalize the time column](#normalize-time)
|
||||
8. [Combine windows](#combine-windows)
|
||||
3. [Join the groups](#join-groups)
|
||||
4. [Map and eval columns](#map-and-eval)
|
||||
2. [Show Tag Values](#show-tag-values)
|
||||
1. [Create cursor](#show-tag-values-cursor)
|
||||
2. [Filter by the measurement](#show-tag-values-measurement-filter)
|
||||
3. [Evaluate the condition](#show-tag-values-evaluate-condition)
|
||||
4. [Retrieve the key values](#show-tag-values-key-values)
|
||||
5. [Find the distinct key values](#show-tag-values-distinct-key-values)
|
||||
3. [Encoding the results](#encoding)
|
||||
|
||||
## <a name="identify-cursors"></a> Identify the cursors
|
||||
## <a name="select-statement"></a> Select Statement
|
||||
|
||||
The InfluxQL query engine works by filling in variables and evaluating the query for the values in each row.
|
||||
The first step of transforming a query is identifying the cursors so we can figure out how to fill them correctly.
|
||||
A cursor is any point in the query that has a **variable or a function call**. Math functions do not count as function
|
||||
calls and are handled in the eval phase.
|
||||
### <a name="identify-cursors"></a> Identify the cursors
|
||||
|
||||
The InfluxQL query engine works by filling in variables and evaluating the query for the values in each row. The first step of transforming a query is identifying the cursors so we can figure out how to fill them correctly. A cursor is any point in the query that has a **variable or a function call**. Math functions do not count as function calls and are handled in the eval phase.
|
||||
|
||||
For the following query, it is easy to identify the cursors:
|
||||
|
||||
SELECT max(usage_user), usage_system FROM telegraf..cpu
|
||||
```
|
||||
SELECT max(usage_user), usage_system FROM telegraf..cpu
|
||||
```
|
||||
|
||||
`max(usage_user)` and `usage_system` are the cursors that we need to fill in for each row. Cursors are global and are not per-field.
|
||||
|
||||
## <a name="identify-query-type"></a> Identify the query type
|
||||
### <a name="identify-query-type"></a> Identify the query type
|
||||
|
||||
There are four types of queries: meta, raw, aggregate, and selector. A meta query is one that retrieves descriptive
|
||||
information about a measurement or series, rather than about the data within the measurement or series.
|
||||
A raw query is one where all of the cursors reference a variable.
|
||||
An aggregate is one where all of the cursors reference a function call.
|
||||
A selector is one where there is exactly one function call that is a selector (such as `max()` or `min()`) and the
|
||||
remaining variables, if there are any, are variables.
|
||||
If there is only one function call with no variables and that function is a selector, then the function type is a selector.
|
||||
There are four types of queries: meta, raw, aggregate, and selector. A meta query is one that retrieves descriptive information about a measurement or series, rather than about the data within the measurement or series. A raw query is one where all of the cursors reference a variable. An aggregate is one where all of the cursors reference a function call. A selector is one where there is exactly one function call that is a selector (such as `max()` or `min()`) and the remaining variables, if there are any, are variables. If there is only one function call with no variables and that function is a selector, then the function type is a selector.
|
||||
|
||||
## <a name="meta-queries"></a>Meta Queries
|
||||
|
||||
### <a name="show-tag-values"></a>SHOW TAG VALUES
|
||||
Show tag values has the full form:
|
||||
|
||||
```
|
||||
SHOW TAG VALUES
|
||||
[ON <database_name>]
|
||||
[FROM <measurement>]
|
||||
WITH KEY [ [<operator> "<tag_key>" | <regular_expression>] | [IN ("<tag_key1>","<tag_key2")]]
|
||||
[WHERE <tag_key> <operator> ['<tag_value>' | <regular_expression>]]
|
||||
[LIMIT_clause]
|
||||
[OFFSET_clause]
|
||||
```
|
||||
|
||||
In flux, for a single `<tag key>`, we can get the tag values:
|
||||
|
||||
```
|
||||
from(db:<database_name>)
|
||||
|> range(start:<start>)
|
||||
|> filter(fn:(r) => r._measurement == <measurement>)
|
||||
|> filter(fn:(r) => <where_clause>)
|
||||
|> group(by:[<tag_key>])
|
||||
|> distinct(column:<tag_key>)
|
||||
|> limit(n: limit_clause)
|
||||
|> group(none:true)
|
||||
```
|
||||
|
||||
TODO(Adam): In some cases `<tag_key>` is instead a set identified by a regex or IN clause. Need to determine the best way to
|
||||
issue a query to get the values for multiple tag keys. The trivial solution is to issue and yield multiple queries.
|
||||
|
||||
TODO(Adam): supporting `<regular_expression>` filters will require some kind of language support since the transpiler is not
|
||||
schema-aware.
|
||||
|
||||
## <a name="data-queries"></a>Data Queries
|
||||
### <a name="group-cursors"></a> Group the cursors
|
||||
|
||||
We group the cursors based on the query type. For raw queries and selectors, all of the cursors are put into the same group. \
|
||||
For aggregates, each function call is put into a separate group so they can be joined at the end.
|
||||
We group the cursors based on the query type. For raw queries and selectors, all of the cursors are put into the same group. \ For aggregates, each function call is put into a separate group so they can be joined at the end.
|
||||
|
||||
### <a name="create-groups"></a> Create the cursors for each group
|
||||
|
||||
|
|
@ -94,36 +57,38 @@ We create the cursors within each group. This process is repeated for every grou
|
|||
|
||||
The cursor is generated using the following template:
|
||||
|
||||
create_cursor = (db, rp="autogen", start, stop=now()) => from(bucket: db+"/"+rp)
|
||||
|> range(start: start, stop: stop)
|
||||
```
|
||||
create_cursor = (db, rp="autogen", start, stop=now()) => from(bucket: db+"/"+rp)
|
||||
|> range(start: start, stop: stop)
|
||||
```
|
||||
|
||||
This is called once per group.
|
||||
|
||||
#### <a name="identify-variables"></a> Identify the variables
|
||||
|
||||
Each of the variables in the group are identified. This involves inspecting the condition to collect the common variables
|
||||
in the expression while also retrieving the variables for each expression within the group.
|
||||
For a function call, this retrieves the variable used as a function argument rather than the function itself.
|
||||
Each of the variables in the group are identified. This involves inspecting the condition to collect the common variables in the expression while also retrieving the variables for each expression within the group. For a function call, this retrieves the variable used as a function argument rather than the function itself.
|
||||
|
||||
If a wildcard is identified in the fields, then the field filter is cleared and only the measurement filter is used.
|
||||
If a regex wildcard is identified, it is added as one of the field filters.
|
||||
If a wildcard is identified in the fields, then the field filter is cleared and only the measurement filter is used. If a regex wildcard is identified, it is added as one of the field filters.
|
||||
|
||||
#### <a name="filter-cursor"></a> Filter by measurement and fields
|
||||
|
||||
A filter expression is generated by using the measurement and the fields that were identified. It follows this template:
|
||||
|
||||
... |> filter(fn: (r) => r._measurement == <measurement> and <field_expr>)
|
||||
```
|
||||
... |> filter(fn: (r) => r._measurement == <measurement> and <field_expr>)
|
||||
```
|
||||
|
||||
The `<measurement>` is equal to the measurement name from the `FROM` clause. The `<field_expr>` section is generated
|
||||
differently depending on the fields that were found. If more than one field was selected, then each of the field filters
|
||||
is combined by using `or` and the expression itself is surrounded by parenthesis. For a non-wildcard field,
|
||||
the following expression is used:
|
||||
The `<measurement>` is equal to the measurement name from the `FROM` clause. The `<field_expr>` section is generated differently depending on the fields that were found. If more than one field was selected, then each of the field filters is combined by using `or` and the expression itself is surrounded by parenthesis. For a non-wildcard field, the following expression is used:
|
||||
|
||||
r._field == <name>
|
||||
```
|
||||
r._field == <name>
|
||||
```
|
||||
|
||||
For a regex wildcard, the following is used:
|
||||
|
||||
r._field =~ <regex>
|
||||
```
|
||||
r._field =~ <regex>
|
||||
```
|
||||
|
||||
If a star wildcard was used, the `<field_expr>` is omitted from the filter expression.
|
||||
|
||||
|
|
@ -131,40 +96,45 @@ If a star wildcard was used, the `<field_expr>` is omitted from the filter expre
|
|||
|
||||
If there was more than one field selected or if one of the fields was some form of wildcard, a pivot expression is generated.
|
||||
|
||||
... |> pivot(rowKey: ["_time"], colKey: ["_field"], valueCol: "_value")
|
||||
```
|
||||
... |> pivot(rowKey: ["_time"], colKey: ["_field"], valueCol: "_value")
|
||||
```
|
||||
|
||||
#### <a name="evaluate-condition"></a> Evaluate the condition
|
||||
|
||||
At this point, generate the `filter` call to evaluate the condition. If there is no condition outside of the
|
||||
time selector, then this step is skipped.
|
||||
At this point, generate the `filter` call to evaluate the condition. If there is no condition outside of the time selector, then this step is skipped.
|
||||
|
||||
#### <a name="perform-grouping"></a> Perform the grouping
|
||||
|
||||
We group together the streams based on the `GROUP BY` clause. As an example:
|
||||
|
||||
> SELECT mean(usage_user) FROM telegraf..cpu WHERE time >= now() - 5m GROUP BY time(5m), host
|
||||
... |> group(by: ["_measurement", "_start", "host"]) |> window(every: 5m)
|
||||
```
|
||||
> SELECT mean(usage_user) FROM telegraf..cpu WHERE time >= now() - 5m GROUP BY time(5m), host
|
||||
... |> group(by: ["_measurement", "_start", "host"]) |> window(every: 5m)
|
||||
```
|
||||
|
||||
If the `GROUP BY time(...)` doesn't exist, `window()` is skipped. Grouping will have a default of [`_measurement`, `_start`],
|
||||
regardless of whether a GROUP BY clause is present. If there are keys in the group by clause, they are concatenated with
|
||||
the default list. If a wildcard is used for grouping, then this step is skipped.
|
||||
If the `GROUP BY time(...)` doesn't exist, `window()` is skipped. Grouping will have a default of [`_measurement`, `_start`], regardless of whether a GROUP BY clause is present. If there are keys in the group by clause, they are concatenated with the default list. If a wildcard is used for grouping, then this step is skipped.
|
||||
|
||||
#### <a name="evaluate-function"></a> Evaluate the function
|
||||
|
||||
If this group contains a function call, the function is evaluated at this stage and invoked on the specific column. As an example:
|
||||
|
||||
> SELECT max(usage_user), usage_system FROM telegraf..cpu
|
||||
val1 = create_cursor(bucket: "telegraf/autogen", start: -5m, m: "cpu", f: "usage_user")
|
||||
val1 = create_cursor(bucket: "telegraf/autogen", start: -5m, m: "cpu", f: "usage_system")
|
||||
inner_join(tables: {val1: val1, val2: val2}, except: ["_field"], fn: (tables) => {val1: tables.val1, val2: tables.val2})
|
||||
|> max(column: "val1")
|
||||
```
|
||||
> SELECT max(usage_user), usage_system FROM telegraf..cpu
|
||||
val1 = create_cursor(bucket: "telegraf/autogen", start: -5m, m: "cpu", f: "usage_user")
|
||||
val1 = create_cursor(bucket: "telegraf/autogen", start: -5m, m: "cpu", f: "usage_system")
|
||||
inner_join(tables: {val1: val1, val2: val2}, except: ["_field"], fn: (tables) => {val1: tables.val1, val2: tables.val2})
|
||||
|> max(column: "val1")
|
||||
```
|
||||
|
||||
For an aggregate, the following is used instead:
|
||||
|
||||
> SELECT mean(usage_user) FROM telegraf..cpu
|
||||
create_cursor(bucket: "telegraf/autogen", start: -5m, m: "cpu", f: "usage_user")
|
||||
|> group(except: ["_field"])
|
||||
|> mean(timeSrc: "_start", columns: ["_value"])
|
||||
```
|
||||
> SELECT mean(usage_user) FROM telegraf..cpu
|
||||
create_cursor(bucket: "telegraf/autogen", start: -5m, m: "cpu", f: "usage_user")
|
||||
|> group(except: ["_field"])
|
||||
|> mean(timeSrc: "_start", columns: ["_value"])
|
||||
```
|
||||
|
||||
If the aggregate is combined with conditions, the column name of `_value` is replaced with whatever the generated column name is.
|
||||
|
||||
|
|
@ -172,11 +142,15 @@ If the aggregate is combined with conditions, the column name of `_value` is rep
|
|||
|
||||
If a function was evaluated and the query type is an aggregate type, then all of the functions need to have their time normalized. If the function is an aggregate, the following is added:
|
||||
|
||||
... |> mean() |> duplicate(column: "_start", as: "_time")
|
||||
```
|
||||
... |> mean() |> duplicate(column: "_start", as: "_time")
|
||||
```
|
||||
|
||||
If it is a selector, then we need to also drop the existing `_time` column with the following:
|
||||
|
||||
... |> max() |> drop(columns: ["_time"]) |> duplicate(column: "_start", as: "_time")
|
||||
```
|
||||
... |> max() |> drop(columns: ["_time"]) |> duplicate(column: "_start", as: "_time")
|
||||
```
|
||||
|
||||
This step does not apply if there are no functions.
|
||||
|
||||
|
|
@ -184,7 +158,9 @@ This step does not apply if there are no functions.
|
|||
|
||||
If there a window operation was added, we then combine each of the function results from the windows back into a single table.
|
||||
|
||||
... |> window(every: inf)
|
||||
```
|
||||
... |> window(every: inf)
|
||||
```
|
||||
|
||||
This step is skipped if there was no window function.
|
||||
|
||||
|
|
@ -192,69 +168,133 @@ This step is skipped if there was no window function.
|
|||
|
||||
If there is only one group, this does not need to be done and can be skipped.
|
||||
|
||||
If there are multiple groups, as is the case when there are multiple function calls, then we perform an `outer_join` using
|
||||
the time and any remaining group keys.
|
||||
If there are multiple groups, as is the case when there are multiple function calls, then we perform an `outer_join` using the time and any remaining group keys.
|
||||
|
||||
### <a name="map-and-eval"></a> Map and eval the columns
|
||||
|
||||
After joining the results if a join was required, then a `map` call is used to both evaluate the math functions and name
|
||||
the columns. The time is also passed through the `map()` function so it is available for the encoder.
|
||||
After joining the results if a join was required, then a `map` call is used to both evaluate the math functions and name the columns. The time is also passed through the `map()` function so it is available for the encoder.
|
||||
|
||||
result |> map(fn: (r) => {_time: r._time, max: r.val1, usage_system: r.val2})
|
||||
```
|
||||
result |> map(fn: (r) => {_time: r._time, max: r.val1, usage_system: r.val2})
|
||||
```
|
||||
|
||||
This is the final result. It will also include any tags in the group key and the time will be located in the `_time` variable.
|
||||
|
||||
TODO(jsternberg): The `_time` variable is only needed for selectors and raw queries. We can actually drop this variable
|
||||
for aggregate queries and use the `_start` time from the group key. Consider whether or not we should do this and
|
||||
if it is worth it.
|
||||
TODO(jsternberg): The `_time` variable is only needed for selectors and raw queries. We can actually drop this variable for aggregate queries and use the `_start` time from the group key. Consider whether or not we should do this and if it is worth it.
|
||||
|
||||
## <a name="show-tag-values"></a> Show Tag Values
|
||||
|
||||
In flux, retrieving the tag values is different than influxql. In influxdb 1.x, tags were included in the index and restricting them by time did not exist or make any sense. In the 2.0 platform, tag keys and values are scoped by time and it is more expensive to retrieve all of the tag values for all time. For this reason, there are some small changes to how the command works and therefore how it is transpiled.
|
||||
|
||||
### <a name="show-tag-values-cursor"></a> Create cursor
|
||||
|
||||
The first step is to construct the initial cursor. This is done similar to a select statement, but we do not filter on the fields.
|
||||
|
||||
```
|
||||
from(bucket: "telegraf/autogen") |>
|
||||
|> range(start: -1h)
|
||||
```
|
||||
|
||||
If no time specifier is specified, as would be expected by most transpiled queries, we default to the last hour. If a time range is present in the `WHERE` clause, that time is used instead.
|
||||
|
||||
### <a name="show-tag-values-measurement-filter"></a> Filter by the measurement
|
||||
|
||||
If a `FROM <measurement>` clause is present in the statement, then we filter by the measurement name.
|
||||
|
||||
```
|
||||
... |> filter(fn: (r) => r._measurement == <measurement>)
|
||||
```
|
||||
|
||||
This step may be skipped if the `FROM` clause is not present. In which case, it will return the tag values for every measurement.
|
||||
|
||||
### <a name="show-tag-values-evaluate-condition"></a> Evaluate the condition
|
||||
|
||||
The condition within the `WHERE` clause is evaluated. It generates a filter in the same way that a [select statement)(#evaluate-condition) would, but with the added assumption that all of the values refer to tags. There is no attempt made at determining if a value is a field or tag.
|
||||
|
||||
### <a name="show-tag-values-key-values"></a> Retrieve the key values
|
||||
|
||||
The key values are retrieved using the `keyValues` function. The `SHOW TAG VALUES` statement requires a tag key filter.
|
||||
|
||||
If a single value is specified with the `=` operator, then that value is used as the single argument to the function.
|
||||
|
||||
```
|
||||
# SHOW TAG VALUES WITH KEY = "host"
|
||||
... |> keyValues(keyCols: ["host"])
|
||||
```
|
||||
|
||||
If the `IN` operator is used, then all of the values are used as a list argument to the `keyValues()`.
|
||||
|
||||
```
|
||||
# SHOW TAG VALUES WITH KEY IN ("host", "region")
|
||||
... |> keyValues(keyCols: ["host", "region"])
|
||||
```
|
||||
|
||||
If any other operation is used, such as `!=` or a regex operator, then a schema function must be used like follows:
|
||||
|
||||
```
|
||||
# SHOW TAG VALUES WITH KEY != "host"
|
||||
... |> keyValues(fn: (schema) => schema.keys |> filter(fn: (col) => col.name != "host"))
|
||||
# SHOW TAG VALUES WITH KEY =~ /host|region/
|
||||
... |> keyValues(fn: (schema) => schema.keys |> filter(fn: (col) => col.name =~ /host|region/))
|
||||
# SHOW TAG VALUES WITH KEY !~ /host|region/
|
||||
... |> keyValues(fn: (schema) => schema.keys |> filter(fn: (col) => col.name !~ /host|region/))
|
||||
```
|
||||
|
||||
TODO(jsternberg): The schema function has not been solidifed, but the basics are that we take the list of group keys and then run a filter using the condition.
|
||||
|
||||
At this point, we have a table with the partition key that is organized by the keys and values of the selected columns.
|
||||
|
||||
### <a name="show-tag-values-distinct-key-values"></a> Find the distinct key values
|
||||
|
||||
We group by the measurement and the key and then use `distinct` on the values. After we find the distinct values, we group these values back by their measurements again so all of the tag values for a measurement are grouped together. We then rename the columns to the expected names.
|
||||
|
||||
```
|
||||
... |> group(by: ["_measurement", "_key"])
|
||||
|> distinct(column: "_value")
|
||||
|> group(by: ["_measurement"])
|
||||
|> rename(columns: {_key: "key", _value: "value"})
|
||||
```
|
||||
|
||||
### <a name="encoding"></a> Encoding the results
|
||||
|
||||
Each statement will be terminated by a `yield()` call. This call will embed the statement id as the result name.
|
||||
The result name is always of type string, but the transpiler will encode an integer in this field so it can be
|
||||
parsed by the encoder. For example:
|
||||
Each statement will be terminated by a `yield()` call. This call will embed the statement id as the result name. The result name is always of type string, but the transpiler will encode an integer in this field so it can be parsed by the encoder. For example:
|
||||
|
||||
result |> yield(name: "0")
|
||||
```
|
||||
result |> yield(name: "0")
|
||||
```
|
||||
|
||||
The edge nodes from the query specification will be used to encode the results back to the user in the JSON format used
|
||||
in 1.x. The JSON format from 1.x is below:
|
||||
The edge nodes from the query specification will be used to encode the results back to the user in the JSON format used in 1.x. The JSON format from 1.x is below:
|
||||
|
||||
{
|
||||
"results": [
|
||||
{
|
||||
"statement_id": 0,
|
||||
"series": [
|
||||
{
|
||||
"name": "_measurement",
|
||||
"tags": {
|
||||
"key": "value"
|
||||
},
|
||||
"columns": [
|
||||
"time",
|
||||
"value"
|
||||
],
|
||||
"values": [
|
||||
[
|
||||
"2015-01-29T21:55:43.702900257Z",
|
||||
2
|
||||
]
|
||||
```
|
||||
{
|
||||
"results": [
|
||||
{
|
||||
"statement_id": 0,
|
||||
"series": [
|
||||
{
|
||||
"name": "_measurement",
|
||||
"tags": {
|
||||
"key": "value"
|
||||
},
|
||||
"columns": [
|
||||
"time",
|
||||
"value"
|
||||
],
|
||||
"values": [
|
||||
[
|
||||
"2015-01-29T21:55:43.702900257Z",
|
||||
2
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
|
||||
The measurement name is retrieved from the `_measurement` column in the results. For the tags, the values in the group
|
||||
key that are of type string are included with both the keys and the values mapped to each other. Any values in the group
|
||||
key that are not strings, like the start and stop times, are ignored and discarded. If the `_field` key is still present
|
||||
in the group key, it is also discarded. For all normal fields, they are included in the array of values for each row.
|
||||
The `_time` field will be renamed to `time` (or whatever the time alias is set to by the query).
|
||||
The measurement name is retrieved from the `_measurement` column in the results. For the tags, the values in the group key that are of type string are included with both the keys and the values mapped to each other. Any values in the group key that are not strings, like the start and stop times, are ignored and discarded. If the `_field` key is still present in the group key, it is also discarded. For all normal fields, they are included in the array of values for each row. The `_time` field will be renamed to `time` (or whatever the time alias is set to by the query).
|
||||
|
||||
The chunking options that existed in 1.x are not supported by the encoder and should not be used. To minimize the amount
|
||||
of breaking code, using a chunking option will be ignored and the encoder will operate as normal, but it will include a
|
||||
message in the result so that a user can be informed that an invalid query option was used. The 1.x format has a field
|
||||
for sending back informational messages in it already.
|
||||
The chunking options that existed in 1.x are not supported by the encoder and should not be used. To minimize the amount of breaking code, using a chunking option will be ignored and the encoder will operate as normal, but it will include a message in the result so that a user can be informed that an invalid query option was used. The 1.x format has a field for sending back informational messages in it already.
|
||||
|
||||
**TODO(jsternberg):** Find a way for a column to be both used as a tag and a field. This is not currently possible
|
||||
because the encoder can't tell the difference between the two.
|
||||
**TODO(jsternberg):** Find a way for a column to be both used as a tag and a field. This is not currently possible because the encoder can't tell the difference between the two.
|
||||
|
|
|
|||
Loading…
Reference in New Issue