[
https://issues.apache.org/jira/browse/BEAM-11801?focusedWorklogId=553851&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-553851
]
ASF GitHub Bot logged work on BEAM-11801:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Feb/21 19:56
Start Date: 17/Feb/21 19:56
Worklog Time Spent: 10m
Work Description: steveniemitz commented on pull request #13964:
URL: https://github.com/apache/beam/pull/13964#issuecomment-780812639
R: @chamikaramj @iemejia
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 553851)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
