You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2020/05/19 17:52:00 UTC

[jira] [Closed] (FLINK-17361) Support creating of a JDBC table using a custom query

     [ https://issues.apache.org/jira/browse/FLINK-17361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aljoscha Krettek closed FLINK-17361.
------------------------------------
    Fix Version/s: 1.11.0
       Resolution: Fixed

release-1.11: c34a4f288deb7dd349c6e52f674d7fa95aa013a1
master: 7bed30ebb88fa4ae3dd277b00f6ea2826fa47d60

> Support creating of a JDBC table using a custom query
> -----------------------------------------------------
>
>                 Key: FLINK-17361
>                 URL: https://issues.apache.org/jira/browse/FLINK-17361
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / API
>            Reporter: Flavio Pompermaier
>            Assignee: Flavio Pompermaier
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>
> In a long discussion on the mailing list it has emerged how it is not possible to create a JDBC table that extract data using a custom query.
> A temporary workaround could be to assign as 'connector.table' the target query.
> However this is undesirable. 
> Moreover, in relation to https://issues.apache.org/jira/browse/FLINK-17360, a query could be actually a statement that requires parameters to be filled by the custom parameter values provider



--
This message was sent by Atlassian Jira
(v8.3.4#803005)