mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-06-30 02:13:33 -04:00
48cb069670
This adds support for the `unsigned_long` type. The type can be now used with the defined math function, both scalar and MV'ed, arithmetic and binary comparison ones. The `to_unsigned_long()` conversion function is also added.
37 lines
1.3 KiB
Text
37 lines
1.3 KiB
Text
[[esql-to_unsigned_long]]
|
|
=== `TO_UNSIGNED_LONG`
|
|
Converts an input value to an unsigned long value.
|
|
|
|
The input can be a single- or multi-valued field or an expression. The input
|
|
type must be of a boolean, date, string or numeric type.
|
|
|
|
Example:
|
|
|
|
[source.merge.styled,esql]
|
|
----
|
|
include::{esql-specs}/ints.csv-spec[tag=to_unsigned_long-str]
|
|
----
|
|
[%header.monospaced.styled,format=dsv,separator=|]
|
|
|===
|
|
include::{esql-specs}/ints.csv-spec[tag=to_unsigned_long-str-result]
|
|
|===
|
|
|
|
Note that in this example, the last conversion of the string isn't
|
|
possible. When this happens, the result is a *null* value. In this case a
|
|
_Warning_ header is added to the response. The header will provide information
|
|
on the source of the failure:
|
|
|
|
`"Line 1:133: evaluation of [TO_UL(str3)] failed, treating result as null. Only first 20 failures recorded."`
|
|
|
|
A following header will contain the failure reason and the offending value:
|
|
|
|
`"java.lang.NumberFormatException: Character f is neither a decimal digit number, decimal point, nor \"e\" notation exponential mark."`
|
|
|
|
|
|
If the input parameter is of a date type, its value will be interpreted as
|
|
milliseconds since the https://en.wikipedia.org/wiki/Unix_time[Unix epoch],
|
|
converted to unsigned long.
|
|
|
|
Boolean *true* will be converted to unsigned long *1*, *false* to *0*.
|
|
|
|
Alias: TO_ULONG, TO_UL
|