You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Update docs for new types
aggregate_metric_double and dense_vector
* Fix typos
* Try to fix applies_to markers
* Fixes
* Mark conversion functions as preview
* Use consistent links
* Mention TO_DENSE_VECTOR
* Refactor 9.2.0 type limitations and fix cross-repo links
Grouped dense_vector and aggregate_metric_double limitations under single bullet with sub-bullets
Added subheading "Partial support in 9.2.0"
Fixed broken elasticsearch:// cross-repo links to /reference/ format
Converted multi-index paragraph to bullet point
Wrapped explanation in note block with bulleted examples
---------
Co-authored-by: Liam Thompson <[email protected]>
{{esql}} does not yet support the following field types:
59
59
60
60
::::{tab-set}
61
61
:::{tab-item} 9.0-9.1
62
+
*`dense_vector`
62
63
* TSDB metrics
63
-
*`counter`
64
-
*`gauge`
64
+
*`counter`
65
+
*`gauge`
65
66
*`aggregate_metric_double`
66
67
:::
67
68
:::{tab-item} 9.2+
68
-
This limitation no longer exists and TSDB metrics are now supported (preview).
69
+
This limitation no longer exists and TSDB metrics and `dense_vector`are now supported (preview).
69
70
:::
70
71
::::
71
72
* Date/time
@@ -104,12 +105,19 @@ Some [field types](/reference/elasticsearch/mapping-reference/field-data-types.m
104
105
*`cartesian_shape`
105
106
106
107
107
-
In addition, when [querying multiple indexes](/reference/query-languages/esql/esql-multi-index.md), it’s possible for the same field to be mapped to multiple types. These fields cannot be directly used in queries or returned in results, unless they’re [explicitly converted to a single type](/reference/query-languages/esql/esql-multi-index.md#esql-multi-index-union-types).
108
+
-In addition, when [querying multiple indexes](/reference/query-languages/esql/esql-multi-index.md), it’s possible for the same field to be mapped to multiple types. These fields cannot be directly used in queries or returned in results, unless they’re [explicitly converted to a single type](/reference/query-languages/esql/esql-multi-index.md#esql-multi-index-union-types).
108
109
109
-
*`dense_vector` field type is partially supported. [`KNN` function](elasticsearch://reference/query-languages/esql/functions-operators/dense-vector-functions.md#esql-knn) queries will work and any field data will be retrieved as part of the results. However, the type will appear as `unsupported` when the `KNN` function is not used.
110
+
#### Partial support in 9.2.0
110
111
111
-
This means that `FROM test` will not retrieve `dense_vector` data. But, `FROM test WHERE KNN("dense_vector_field", [0, 1, 2, ...])` will retrieve data.
112
+
* {applies_to}`stack: preview 9.2.0` The following types are only partially supported on 9.2.0. This is fixed in 9.2.1:
113
+
*`dense_vector`: The [`KNN` function](/reference/query-languages/esql/functions-operators/dense-vector-functions.md#esql-knn) and the [`TO_DENSE_VECTOR` function](/reference/query-languages/esql/functions-operators/type-conversion-functions.md#esql-to_dense_vector) will work and any field data will be retrieved as part of the results. However, the type will appear as `unsupported` when these functions are not used.
114
+
*`aggregate_metric_double`: Using the [`TO_AGGREGATE_METRIC_DOUBLE` function](/reference/query-languages/esql/functions-operators/type-conversion-functions.md#esql-to_aggregate_metric_double) will work and any field data will be retrieved as part of the results. However, the type will appear as `unsupported` if this function is not used.
112
115
116
+
:::{note}
117
+
This means that a simple query like `FROM test` will not retrieve `dense_vector` or `aggregate_metric_double` data. However, using the appropriate functions will work:
118
+
*`FROM test WHERE KNN("dense_vector_field", [0, 1, 2, ...])`
119
+
*`FROM test | EVAL agm_data = TO_AGGREGATE_METRIC_DOUBLE(aggregate_metric_double_field)`
0 commit comments