You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2021/05/04 06:59:00 UTC

[jira] [Updated] (BEAM-12253) Read.UnboundedSourceAsSDFRestrictionTracker doesn't use cache for readers in getProgress

     [ https://issues.apache.org/jira/browse/BEAM-12253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismaël Mejía updated BEAM-12253:
--------------------------------
    Resolution: Fixed
        Status: Resolved  (was: In Progress)

> Read.UnboundedSourceAsSDFRestrictionTracker doesn't use cache for readers in getProgress
> ----------------------------------------------------------------------------------------
>
>                 Key: BEAM-12253
>                 URL: https://issues.apache.org/jira/browse/BEAM-12253
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Sam Whittle
>            Assignee: Sam Whittle
>            Priority: P2
>             Fix For: 2.31.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> https://github.com/apache/beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/io/Read.java#L963
> In getProgress, if currentReader == null a new reader is constructed from the restriction checkpoint.  I think that we should consult the reader cache as creating readers is sometimes expensive.
> I observed in Nexmark pipelines that readers were being created at this location.



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