hqbhoho commented on code in PR #8419:
URL: https://github.com/apache/gravitino/pull/8419#discussion_r2324561636
##########
trino-connector/integration-test/src/test/java/org/apache/gravitino/trino/connector/integration/test/TrinoQueryTestTool.java:
##########
@@ -85,6 +85,13 @@ public static void main(String[] args) throws Exception {
"Additional parameters that can replace the value of ${key} in the
testers contents, "
+ "example: --params=key1,v1;key2,v2");
+ options.addOption(
+ "trino_worker_num",
+ true,
+ "Specify the number of Trino worker, the default value is 0."
Review Comment:
Currently, it will use a single node that functions as both a coordinator
and worker in default CI behavior.
In production deploy, it will use independent worker. There is no limit to
the number of Trino workers but at least one worker is required.
More worker may need more resources, we do not prefer change default CI
behavior. So I add a configuration `trino-worker-num` to facilitate deploying a
distributed environment for testing purposes. If `trino-worker-num` = 0, it
will use the current implementation which use a single node that functions as
both a coordinator and worker.
If run in a distributed environment is necessary, you can run integration
tests with a distributed environment which have 3 independent workers like this:
```
bash trino-connector/integration-test/trino-test-tools/trino_test.sh
--test_set=jdbc-mysql --trino_worker_num=3
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
