[Core] CallOptionsConfig.setUseTimeout also affects streaming RPCs

[AdamBSteele]

The documentation for CallOptionsConfig.Builder.setUseTimeout() states that setUseTimeout only affects "unary RPCS like mutations." Per my testing, it also affects (streaming) readRows operations.

Environment details

Version(s): java-bigtable-hbase v1.18.1

Steps to reproduce

(See code below)

1. Start emulator with latency injection

• I used this fork to introduce 50ms latency to all ReadRows calls with command line arg: --inject-latency="ReadRows:p0:50ms"

2. In CallOptionsConfig:

• Set useTimeout = false.
• Use short values for ReadRowsRpcAttemptTimeoutMs and ReadRowsRpcTimeoutMs.

3. Call readRows

Results

• Expected: Calls will throw timeouts
• Actual: Calls will succeed.

Note: if you set usetTimeout = true, you will see timeouts

Code example

    final CallOptionsConfig callOptions = CallOptionsConfig.builder()
        .setReadRowsRpcAttemptTimeoutMs(10) // Short
        .setReadRowsRpcTimeoutMs(10) // Short
        .setUseTimeout(false) // If you set this to true, you'll see timeouts.
        .build();
    final BigtableOptions bigtableOptions = BigtableOptions.builder()
        .enableEmulator("localhost:9000")
        .setCallOptionsConfig(callOptions)
        .setInstanceId("example")
        .setProjectId("example")
        .setUserAgent("example")
        .build();
    final BigtableSession session = new BigtableSession(bigtableOptions);

    // Create table
    session.getTableAdminClient().createTable(CreateTableRequest.newBuilder().setTableId("tbl").build());

    // Scan table
    System.out.println("This stream operation should timeout");
    session.getDataClient().readRows(
        ReadRowsRequest.newBuilder().setTableName("/tables/tbl").build()
    ).next(10_000);
    System.out.println("Operation succeeded");

External references such as API reference guides

javadoc: CallOptionsConfig.Builder