[
https://issues.apache.org/jira/browse/FLINK-15686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz closed FLINK-15686.
------------------------------------
Resolution: Fixed
Fixed in:
master: 8d85f85e265158e4ffbef4718f31306562652f98
1.10: bcb2b707be5b814add6c3f44f9a7079016f54c57
> SELECT 'ABC'; does not work in sql-client
> -----------------------------------------
>
> Key: FLINK-15686
> URL: https://issues.apache.org/jira/browse/FLINK-15686
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Client
> Affects Versions: 1.10.0
> Reporter: Dawid Wysakowicz
> Assignee: Dawid Wysakowicz
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> A query like {{SELECT 'abc';}} fails in sql-client with blink planner enabled
> with an error:
> {code}
> org.apache.flink.table.api.ValidationException: Type CHAR(3) of table field
> 'EXPR$0' does not match with the physical type STRING of the 'EXPR$0' field
> of the TableSink consumed type.
> {code}
> The reason is that those sinks do not properly support new type system. There
> is no good way to define schema and consumed data type so that they match. We
> should update the in-memory sinks in sql-client to work with the legacy type
> system for now until the retract and upsert sinks work properly with the new
> type system.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
