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 2021/01/09 17:13:05 UTC

[jira] [Commented] (BEAM-11215) Support more granular splitting in BigQueryStorageStreamSource

    [ https://issues.apache.org/jira/browse/BEAM-11215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261910#comment-17261910 ] 

Beam JIRA Bot commented on BEAM-11215:
--------------------------------------

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.


> Support more granular splitting in BigQueryStorageStreamSource
> --------------------------------------------------------------
>
>                 Key: BEAM-11215
>                 URL: https://issues.apache.org/jira/browse/BEAM-11215
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-gcp
>    Affects Versions: 2.25.0
>            Reporter: Kenneth Jung
>            Priority: P2
>              Labels: stale-P2
>
> The BigQuery storage API supports partitioning of streams in the API. However, the partitioning granularity is not sufficient for some pipelines, for which it is desirable to be able to dynamically rebalance down to the level of individual rows. This can be implemented by storing both the stream ID and an offset range as components of a stream source, as opposed to a stream ID only.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)