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 2022/04/27 17:28:00 UTC

[jira] [Commented] (BEAM-13684) Consider adding information to ProcessBundleRequest indicating there is no existing state

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

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

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.


> Consider adding information to ProcessBundleRequest indicating there is no existing state
> -----------------------------------------------------------------------------------------
>
>                 Key: BEAM-13684
>                 URL: https://issues.apache.org/jira/browse/BEAM-13684
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model
>            Reporter: Sam Whittle
>            Priority: P2
>              Labels: stale-P2
>
> This allows for skipping all state fetches made during processing this key, preloading the cache with empty values for the key, or extending the cache to include this negative state information to avoid fetches as long as no state is evicted for the key.
> This is particularly beneficial in sparse key streaming pipelines where such new keys are common.
> It could also be used to avoid fetches in batch pipelines where there is no persisted state.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)