[
https://issues.apache.org/jira/browse/BEAM-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132140#comment-17132140
]
Beam JIRA Bot commented on BEAM-728:
------------------------------------
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.
> 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
> Priority: P2
> Labels: stale-P2
>
> 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
(v8.3.4#803005)
