[
https://issues.apache.org/jira/browse/BEAM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132090#comment-17132090
]
Beam JIRA Bot commented on BEAM-1197:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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)
