You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Steve Niemitz (Jira)" <ji...@apache.org> on 2021/02/11 15:55:00 UTC

[jira] [Work started] (BEAM-11801) BigtableIO should not set useCachedDataPool when using an emulator

     [ https://issues.apache.org/jira/browse/BEAM-11801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on BEAM-11801 started by Steve Niemitz.
--------------------------------------------
> 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
>            Priority: P2
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)