beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eugene Kirpichov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-673) Data locality for Read.Bounded
Date Wed, 26 Apr 2017 01:08:04 GMT

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

Eugene Kirpichov commented on BEAM-673:
---------------------------------------

On second thought, this might be related to SDF: processing different restrictions of the
same element may have different requirements.

Or more like: a design for DoFn's giving hints to runners about their resource requirements
would need to include some data dependence. I don't have a good idea about how to express
it in a way that will be modular and will combine well with the rest of the Beam model and
various tricks runners are allowed to do (such as fusion or materialization).

> Data locality for Read.Bounded
> ------------------------------
>
>                 Key: BEAM-673
>                 URL: https://issues.apache.org/jira/browse/BEAM-673
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>            Reporter: Amit Sela
>            Assignee: Ismaël Mejía
>             Fix For: First stable release
>
>
> In some distributed filesystems, such as HDFS, we should be able to hint to Spark the
preferred locations of splits.
> Here is an example of how Spark does that for Hadoop RDDs:
> https://github.com/apache/spark/blob/branch-1.6/core/src/main/scala/org/apache/spark/rdd/NewHadoopRDD.scala#L249



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message