[
https://issues.apache.org/jira/browse/KUDU-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18067034#comment-18067034
]
ASF subversion and git services commented on KUDU-3750:
-------------------------------------------------------
Commit 68f10dd41067059260a5fb5c725b178b69c38aed in kudu's branch
refs/heads/master from Marton Greber
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=68f10dd41 ]
KUDU-3750 python: per-test master/tserver flags
Add @master_flags and @tserver_flags decorators to KuduTestBase.
Tests needing specific cluster flags spin up a dedicated
mini-cluster; all other tests share a single class-level cluster.
Unlike Java where every test runs on a fresh cluster, the shared
cluster keeps the Python test suite fast since Python tests run on
Jenkins builders and cannot utilize dist-test.
Change-Id: I648adcd692b2093e99cb541b9f809ef0bb6bec0f
Reviewed-on: http://gerrit.cloudera.org:8080/24099
Reviewed-by: Alexey Serbin <[email protected]>
Tested-by: Marton Greber <[email protected]>
Reviewed-by: Gabriella Lotz <[email protected]>
> Allow setting test specific master/tserver flags in Python client tests
> -----------------------------------------------------------------------
>
> Key: KUDU-3750
> URL: https://issues.apache.org/jira/browse/KUDU-3750
> Project: Kudu
> Issue Type: Improvement
> Reporter: Marton Greber
> Assignee: Marton Greber
> Priority: Minor
>
> The Python client test setup does not allow to set master/tserver flags on a
> per test basis.
> Right now we just set a given set of flags on mini cluster startup and thats
> it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)