SQL: Implement CONVERT, an alternative to CAST#34660
Conversation
`CONVERT` works exactly like cast with slightly different syntax: `CONVERT(<value>, <data_type)` as opposed to `CAST(<value> AS <data_type>)` Moreover it support format of the MS-SQL data types `SQL_<type>`, e.g.: `SQL_INTEGER` Closes: elastic#34513
|
Pinging @elastic/es-search-aggs |
|
@costin @astefan Instead of In this case, the user won't get a |
|
Definitely UNSUPPORTED from usability point of view. It is not an invalid data type, but rather a valid one we do not support yet. |
costin
left a comment
There was a problem hiding this comment.
LGTM.
+1 on using UNSUPPORTED instead of null.
| DATE( JDBCType.TIMESTAMP, Timestamp.class, Long.BYTES, 24, 24); | ||
| // @formatter:on | ||
|
|
||
| public static final String MSSQL_DATATYPE_PREFIX = "SQL_"; |
There was a problem hiding this comment.
It's not so much MSSQL as ODBC spec.
There was a problem hiding this comment.
Sure, replaced all MSSQL with ODBC.
astefan
left a comment
There was a problem hiding this comment.
LGTM. Left just one minor comment related to docs.
| ; | ||
|
|
||
|
|
||
| conversionStringToIntConvertESDataType |
There was a problem hiding this comment.
I would put this example first and the odbc one second, in order of familiarity/usage?
|
retest this please |
1 similar comment
|
retest this please |
|
Try merging master again - hopefully it fixes the external failure. |
`CONVERT` works exactly like cast with slightly different syntax: `CONVERT(<value>, <data_type)` as opposed to `CAST(<value> AS <data_type>)` Moreover it support format of the MS-SQL data types `SQL_<type>`, e.g.: `SQL_INTEGER` Closes: #34513
|
Backported to |
* master: (24 commits) ingest: better support for conditionals with simulate?verbose (elastic#34155) [Rollup] Job deletion should be invoked on the allocated task (elastic#34574) [DOCS] .Security index is never auto created (elastic#34589) CCR: Requires soft-deletes on the follower (elastic#34725) re-enable bwc tests (elastic#34743) Empty GetAliases authorization fix (elastic#34444) INGEST: Document Processor Conditional (elastic#33388) [CCR] Add total fetch time leader stat (elastic#34577) SQL: Support pattern against compatible indices (elastic#34718) [CCR] Auto follow pattern APIs adjustments (elastic#34518) [Test] Remove dead code from ExceptionSerializationTests (elastic#34713) A small typo in migration-assistance doc (elastic#34704) ingest: processor stats (elastic#34724) SQL: Implement IN(value1, value2, ...) expression. (elastic#34581) Tests: Add checks to GeoDistanceQueryBuilderTests (elastic#34273) INGEST: Rename Pipeline Processor Param. (elastic#34733) Core: Move IndexNameExpressionResolver to java time (elastic#34507) [DOCS] Force Merge: clarify execution and storage requirements (elastic#33882) TESTING.asciidoc fix examples using forbidden annotation (elastic#34515) SQL: Implement `CONVERT`, an alternative to `CAST` (elastic#34660) ...
`CONVERT` works exactly like cast with slightly different syntax: `CONVERT(<value>, <data_type)` as opposed to `CAST(<value> AS <data_type>)` Moreover it support format of the MS-SQL data types `SQL_<type>`, e.g.: `SQL_INTEGER` Closes: #34513
CONVERTworks exactly like cast with slightly different syntax:CONVERT(<value>, <data_type)as opposed toCAST(<value> AS <data_type>)Moreover it support format of the MS-SQL data types
SQL_<type>,e.g.:
SQL_INTEGERCloses: #34513