[DOCS] Adds data nanos transform limitation (#53826)
This commit is contained in:
parent
8b3ef4ac21
commit
5f45780577
|
@ -96,6 +96,6 @@ same mapping parameters than with the `date` field can be used.
|
||||||
[[date-nanos-limitations]]
|
[[date-nanos-limitations]]
|
||||||
==== Limitations
|
==== Limitations
|
||||||
|
|
||||||
Aggregations are still on millisecond resolution, even when using a
|
Aggregations are still on millisecond resolution, even when using a `date_nanos`
|
||||||
`date_nanos` field.
|
field. This limitation also affects <<transforms,{transforms}>>.
|
||||||
|
|
||||||
|
|
|
@ -206,3 +206,10 @@ this entity will not be updated.
|
||||||
If using a `sync.time.field` that represents the data ingest time and using a
|
If using a `sync.time.field` that represents the data ingest time and using a
|
||||||
zero second or very small `sync.time.delay`, then it is more likely that this
|
zero second or very small `sync.time.delay`, then it is more likely that this
|
||||||
issue will occur.
|
issue will occur.
|
||||||
|
|
||||||
|
[[transform-date-nanos]]
|
||||||
|
==== Support for date nanoseconds data type
|
||||||
|
|
||||||
|
If your data uses the <<date_nanos,date nanosecond data type>>, aggregations
|
||||||
|
are nonetheless on millisecond resolution. This limitation also affects the
|
||||||
|
aggregations in your {transforms}.
|
Loading…
Reference in New Issue