[
https://issues.apache.org/jira/browse/FLINK-25788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Nuyanzin updated FLINK-25788:
------------------------------------
Description:
Currently the only work around to see available connectors is to create a table
for non-existing connector and run sql over that table. In Exception there will
be a list of available connectors.
The idea is to have command like
{code:sql}
Flink SQL> SHOW CONNECTORS;
+----------------+--------+
| connector name | type |
+----------------+--------+
| opensearch | sink |
| datagen | source |
| blackhole | sink |
| print | sink |
+----------------+--------+
5 rows in set
{code}
was:
Currently the only work around to see available connectors is to create a table
for non-existing connector and run sql over that table. In Exception there will
be a list of available connectors.
The idea is to have command like
{code:sql}
Flink SQL> SHOW CONNECTORS;
+----------------+
| connector name |
+----------------+
| filesystem |
| opensearch |
| datagen |
| blackhole |
| print |
+----------------+
5 rows in set
{code}
> Add show connectors command
> ---------------------------
>
> Key: FLINK-25788
> URL: https://issues.apache.org/jira/browse/FLINK-25788
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Common, Table SQL / API
> Reporter: Sergey Nuyanzin
> Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available
>
> Currently the only work around to see available connectors is to create a
> table for non-existing connector and run sql over that table. In Exception
> there will be a list of available connectors.
> The idea is to have command like
> {code:sql}
> Flink SQL> SHOW CONNECTORS;
> +----------------+--------+
> | connector name | type |
> +----------------+--------+
> | opensearch | sink |
> | datagen | source |
> | blackhole | sink |
> | print | sink |
> +----------------+--------+
> 5 rows in set
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
