Steve Niemitz created BEAM-11801:
------------------------------------
Summary: BigtableIO should not set useCachedDataPool when using an
emulator
Key: BEAM-11801
URL: https://issues.apache.org/jira/browse/BEAM-11801
Project: Beam
Issue Type: Bug
Components: io-java-gcp
Reporter: Steve Niemitz
Assignee: Steve Niemitz
Because of how the underlying Bigtable client library works, the first channel
pool to be created when useCachedDataPool is set will persist for the lifetime
of the process.
However, running tests with a Bigtable emulator may mean that multiple
concurrent hosts are being used (one for each test for example).
As a workaround for now, we should not set useCachedDataPool if an emulator
host is set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)