mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-26 08:07:27 -04:00
Part of https://github.com/elastic/elasticsearch/issues/106679 * Copy the `ql` project into a different project _just for esql_, call it `esql-core`. * Make `esql` depend only on the latter. * Fix `EsqlNodeSubclassTests`; I'm confused why this didn't bite us earlier. * Update the warning regexes in some csv tests as the exceptions have other package names now. **Note to reviewers:** Exclude the first commit when viewing the diff, as that contains only the actual copying of `ql`. The remaining commits are the actually meaningful ones. _The `build.gradle` files probably require the most attention._
24 lines
912 B
Text
Generated
24 lines
912 B
Text
Generated
// This is generated by ESQL's AbstractFunctionTestCase. Do no edit it. See ../README.md for how to regenerate it.
|
|
|
|
*Example*
|
|
|
|
[source.merge.styled,esql]
|
|
----
|
|
include::{esql-specs}/ints.csv-spec[tag=to_int-long]
|
|
----
|
|
[%header.monospaced.styled,format=dsv,separator=|]
|
|
|===
|
|
include::{esql-specs}/ints.csv-spec[tag=to_int-long-result]
|
|
|===
|
|
|
|
Note that in this example, the last value of the multi-valued field cannot be converted as an integer.
|
|
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:61: evaluation of [TO_INTEGER(long)] failed, treating result as null. Only first 20 failures recorded."`
|
|
|
|
A following header will contain the failure reason and the offending value:
|
|
|
|
`"org.elasticsearch.xpack.esql.core.InvalidArgumentException: [501379200000] out of [integer] range"`
|
|
|
|
|