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

Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2017/08/24 21:05:00 UTC

[jira] [Assigned] (BEAM-728) Javadoc should clearly separate facts from runner requirements

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

Davor Bonaci reassigned BEAM-728:
---------------------------------

    Assignee:     (was: Davor Bonaci)

> Javadoc should clearly separate facts from runner requirements
> --------------------------------------------------------------
>
>                 Key: BEAM-728
>                 URL: https://issues.apache.org/jira/browse/BEAM-728
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Frances Perry
>
> The javadoc for View.asMap() says the map needs to fit in memory. That's not true in all runners. (For example, Dataflow has distributed map support.) 
> https://github.com/apache/incubator-beam/blob/master/sdks/java/core/src/main/java/org/apache/beam/sdk/transforms/View.java
> This is likely just one specific case of a more general issue -- different runners will have common constraints on the scalability of portions of the model. Currently these are documented in the capability matrix on the website, but for usability we should consider surfacing these constraints on particularly relevant methods. But keeping things in sync in multiple locations is hard...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)