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
Currently esType is just a lowercase of the DataType.
Since esType is used for calls to unmappedType() this must be fixed, as for DATETIME it should be date and for ES-SQL types only like DATE and INTERVAL types it should be unsupported operation.
The text was updated successfully, but these errors were encountered:
Since introduction of data types that don't have a corresponding type
in ES the `esType` is error-prone when used for `unmappedType()` calls.
Moreover since the renaming of `DATE` to `DATETIME` and the introduction
of an actual date-only `DATE` the `esType` would return `datetime` which
is not a valid type for ES mapping.
Fixes: elastic#38051
Since introduction of data types that don't have a corresponding type
in ES the `esType` is error-prone when used for `unmappedType()` calls.
Moreover since the renaming of `DATE` to `DATETIME` and the introduction
of an actual date-only `DATE` the `esType` would return `datetime` which
is not a valid type for ES mapping.
Fixes: #38051
Since introduction of data types that don't have a corresponding type
in ES the `esType` is error-prone when used for `unmappedType()` calls.
Moreover since the renaming of `DATE` to `DATETIME` and the introduction
of an actual date-only `DATE` the `esType` would return `datetime` which
is not a valid type for ES mapping.
Fixes: #38051
Currently
esType
is just a lowercase of the DataType.Since esType is used for calls to
unmappedType()
this must be fixed, as forDATETIME
it should bedate
and for ES-SQL types only likeDATE
andINTERVAL
types it should be unsupported operation.The text was updated successfully, but these errors were encountered: