You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/07/02 17:25:01 UTC
[jira] [Commented] (BEAM-1197) Slowly-changing external data as a
side input
[ https://issues.apache.org/jira/browse/BEAM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150468#comment-17150468 ]
Beam JIRA Bot commented on BEAM-1197:
-------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2.
> Slowly-changing external data as a side input
> ---------------------------------------------
>
> Key: BEAM-1197
> URL: https://issues.apache.org/jira/browse/BEAM-1197
> Project: Beam
> Issue Type: Wish
> Components: beam-model
> Reporter: Eugene Kirpichov
> Priority: P3
>
> I've seen repeatedly the following pattern: a user wants to join a PCollection against a slowly-changing external dataset: e.g. a file on GCS, or a Bigtable, etc.
> Side inputs come to mind, but current side input mechanisms don't allow for something like periodically reloading the side input.
> The best hacky solution I came up with for one use case is documented here: http://stackoverflow.com/questions/41254028/can-dataflow-sideinput-be-updated-per-window-by-reading-a-gcs-bucket/41271159#41271159 , we need to do better than this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)