apache/beam

Python DirectRunner _PubSubReadEvaluator creates new client per bundle

Open

#19,712 opened on Jun 4, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Java (4,097 forks)batch import
P3bugcoregood first issuepython

Repository metrics

Stars
 (7,313 stars)
PR merge metrics
 (Avg merge 6d) (243 merged PRs in 30d)

Description

Lots of credential fetches. Similar to https://issues.apache.org/jira/browse/BEAM-2264 but in this case the DirectRunner implementation seems to be creating a new client for each bundle: https://github.com/apache/beam/blob/d5d7a7b7d0408d8435031e7bfce1abe2227115f5/sdks/python/apache_beam/runners/direct/transform_evaluator.py#L474

From: https://stackoverflow.com/questions/57010426/dataflow-access-to-pubsub-access-tokens

Imported from Jira BEAM-7763. Original Jira may contain additional context. Reported by: udim.

Contributor guide

Research direction
Investigate how to cache or reuse the PubSub client across bundles in DirectRunner's PubSubReadEvaluator.
Tech stack
python
Domain
backenddata
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75