Stop invoking table batching lambdas in system tests

[patchwork01]

Background

Split from:

• Update multiple tables system tests for parallelised components #1918

Child issue of:

• Parallelise system tests #1794

Related to:

• Multiple tables system test should use table batching lambdas in its own instance #2016

We'd like to be able to run system tests in parallel. Each system test runs in its own Sleeper table, but right now several operations are done across all tables at once. This means eg. garbage collection will affect all running system tests when it's invoked.

Description

In order to isolate system tests from one another when they run in parallel in the same instance, we'd like to change the places where system tests currently invoke table batching lambdas.

Instead of invoking the table batching lambdas, we can match the implementation of the lambdas, but instead of batching over all the tables (or all the online tables), we can batch over the tables that are active in the current test, with SystemTestInstanceContext.streamTableProperties.

Analysis

Here are the relevant operations:

• Compaction job creation
• Partition splitting
• Garbage collection
• Table metrics

We've split out a separate issue to convert the multiple tables test to run in its own instance, and switch it back to invoke the table batching lambdas:

• Multiple tables system test should use table batching lambdas in its own instance #2016

We could make sure we keep the code to invoke the table batching lambdas around, so that we can use it for that.

We did some work on this here, which we could reuse:

• Issue 2003 - Stop invoking table batching lambdas in system tests #2019

[patchwork01]

The following issue replaces this:

• Enable schedule rules by default in system tests #3722