[
https://issues.apache.org/jira/browse/FLINK-32030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Weise resolved FLINK-32030.
----------------------------------
Resolution: Fixed
> SQL Client gateway mode should accept URLs
> ------------------------------------------
>
> Key: FLINK-32030
> URL: https://issues.apache.org/jira/browse/FLINK-32030
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Client, Table SQL / Gateway
> Affects Versions: 1.17.0
> Reporter: Alexander Fedulov
> Assignee: Alexander Fedulov
> Priority: Major
> Labels: pull-request-available
>
> Currently, the _--endpoint_ parameter has to be specified in the
> _InetSocketAddress_ format, i.e. _hostname:port._ While this works fine for
> basic use cases, it does not support the placement of the gateway behind a
> proxy or using an Ingress for routing to a specific Flink cluster based on
> the URL path. I.e. it expects
> _[some.hostname.com:9001|http://some.hostname.com:9001/]_ to directly serve
> requests on _[some.hostname.com:9001/v1|http://some.hostname.com:9001/v1]_ .
> Mapping to a non-root location, i.e.
> _[some.hostname.com:9001/flink-clusters/sql-preview-cluster-1/v1|http://some.hostname.com:9001/flink-clusters/sql-preview-cluster-1/v1]_
> is not supported.
>
> Since the client talks to the gateway via its REST endpoint, the right format
> for the _--endpoint_ parameter is {_}URL{_}, not _InetSocketAddress_ .
> The same _--endpoint_ parameter can be reused if the changes are implemented
> in a backwards-compatible way.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
