GitHub user kmaehashi opened a pull request:

    https://github.com/apache/spark/pull/7632

    Cosmetic fix for usage of spark-ec2 --ebs-vol-num option

    The last line of the usage seems ugly.
    
    ```
    $ spark-ec2 --help
    <snip>
      --ebs-vol-num=EBS_VOL_NUM
                            Number of EBS volumes to attach to each node as
                            /vol[x]. The volumes will be deleted when the
                            instances terminate. Only possible on EBS-backed 
AMIs.
                            EBS volumes are only attached if --ebs-vol-size >
                            0.Only support up to 8 EBS volumes.
    ```
    
    After applying this patch:
    
    ```
    $ spark-ec2 --help
    <snip>
      --ebs-vol-num=EBS_VOL_NUM
                            Number of EBS volumes to attach to each node as
                            /vol[x]. The volumes will be deleted when the
                            instances terminate. Only possible on EBS-backed 
AMIs.
                            EBS volumes are only attached if --ebs-vol-size > 0.
                            Only support up to 8 EBS volumes.
    ```
    
    As this is a trivial thing I didn't create JIRA for this.

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

    $ git pull https://github.com/kmaehashi/spark spark-ec2-cosmetic-fix

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

    https://github.com/apache/spark/pull/7632.patch

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

    This closes #7632
    
----
commit 526c118a85a03ff14bd8a0a6e22b03f9dc6755fd
Author: Kenichi Maehashi <[email protected]>
Date:   2015-07-24T03:30:26Z

    cosmetic fix for spark-ec2 --ebs-vol-num option usage

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to