beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-918) Let users set STORAGE_LEVEL via SparkPipelineOptions.
Date Wed, 16 Nov 2016 15:33:58 GMT


ASF GitHub Bot commented on BEAM-918:

GitHub user jbonofre opened a pull request:

    [BEAM-918] Allow users to define the storage level via pipeline options

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [X] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [X] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [X] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [X] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](

You can merge this pull request into a Git repository by running:

    $ git pull BEAM-918

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1370
commit fc3f2ab4a3dd970025f73573f26541ce2f6ed2cd
Author: Jean-Baptiste Onofré <>
Date:   2016-11-16T15:32:28Z

    [BEAM-918] Allow users to define the storage level via pipeline options


> Let users set STORAGE_LEVEL via SparkPipelineOptions.
> -----------------------------------------------------
>                 Key: BEAM-918
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-spark
>            Reporter: Amit Sela
>            Assignee: Jean-Baptiste Onofré
> 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

View raw message