beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (BEAM-918) Let users set STORAGE_LEVEL via SparkPipelineOptions.
Date Thu, 01 Dec 2016 13:35:58 GMT

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

Jean-Baptiste Onofré resolved BEAM-918.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.4.0-incubating

> Let users set STORAGE_LEVEL via SparkPipelineOptions.
> -----------------------------------------------------
>
>                 Key: BEAM-918
>                 URL: https://issues.apache.org/jira/browse/BEAM-918
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-spark
>            Reporter: Amit Sela
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 0.4.0-incubating
>
>
> Spark provides different "STORAGE_LEVEL"s for caching RDDs (disk, memory, ser/de, etc.).
> The runner decides on caching when necessary, for example when a RDD is accessed repeatedly.
>  
> For batch, we can let users set their preferred STORAGE_LEVEL via SparkPipelineOptions.
> Note: for streaming we force a "MEMORY_ONLY", since (among other things) the runner heavily
relies on stateful operations, and it's natural for streaming to happen in memory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message