[
https://issues.apache.org/jira/browse/KUDU-3540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabor Zele updated KUDU-3540:
-----------------------------
Summary: "kudu master/tserver list -columns http-addresses" should return
complete URL (was: "kudu master/tserver list -columns http-addresses" should
give complete URL)
> "kudu master/tserver list -columns http-addresses" should return complete URL
> -----------------------------------------------------------------------------
>
> Key: KUDU-3540
> URL: https://issues.apache.org/jira/browse/KUDU-3540
> Project: Kudu
> Issue Type: Wish
> Reporter: Gabor Zele
> Priority: Minor
>
> If I use the Kudu CLI command "kudu master/tserver list -columns
> http-addresses" to get infromation about how to conenct to the web UI/API of
> these services, it will only report back the hostname/port, not the complete
> URL. So the get a complete URL, I need to know if the web UI/API is operating
> with TLS or not.
> If I use the "/dump-entities" WEB API endpoint on one of the masters to get
> this info, I'll get a complete URL (as "http_addrs[]").
> Also, if I use "-format json" to get a json output from these commands, there
> are more differnces to "/dump-entities":
> CLI has "rpc-addresses" and "http-adressess", while WEB API has "rpc_addrs"
> and "http_addrs" (and the latter emits full URL).
> Web API outputs a json array for both (even for a single adress), I'm not
> sure about the CLI, for a single address it only shows a single value, not an
> array.
> It would be nince if the output of "kudu master/tserver list format json" and
> what I get from "/dump-entites" would be the same, so I could use the same
> json parsing no matter where the data is coming from. Maybe you could add the
> columns "rpc_addrs" and "http_addrs" to the CLI with the same output as in
> "/dump-entities", that wouldn't break compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
