[
https://issues.apache.org/jira/browse/KUDU-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Greber updated KUDU-3602:
--------------------------------
Description:
Change https://gerrit.cloudera.org/#/c/20868/ introduced tests for checking the
content-type headers on master/tserver endpoints.
The expected set of \{endpoint name, content-type header\} is pre-defined in
test_util.cc.
If one endpoint changes, or a new one is added these maps need to be updated.
It would be nice to get rid of this pre-defined structure and make this
\{endpoint,vcontent-type header\} enumeration automatic.
was:
Change https://gerrit.cloudera.org/#/c/20868/ introduced tests for checking the
content-type headers on master/tserver endpoints.
The expected set of \{endpoint name, content-type header\} is pre-defined in
test_util.cc.
If one endpoint changes, or a new one is added these maps need to be updated.
It would be nice to get rid of this pre-defined structure and make this
{endpoint,vcontent-type header} enumeration automatic.
> Gather {endpoint name, content-type header} automatically for tests
> -------------------------------------------------------------------
>
> Key: KUDU-3602
> URL: https://issues.apache.org/jira/browse/KUDU-3602
> Project: Kudu
> Issue Type: Improvement
> Reporter: Marton Greber
> Priority: Major
>
> Change https://gerrit.cloudera.org/#/c/20868/ introduced tests for checking
> the content-type headers on master/tserver endpoints.
> The expected set of \{endpoint name, content-type header\} is pre-defined in
> test_util.cc.
> If one endpoint changes, or a new one is added these maps need to be updated.
> It would be nice to get rid of this pre-defined structure and make this
> \{endpoint,vcontent-type header\} enumeration automatic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
