GitHub user philipphoffmann opened a pull request:
https://github.com/apache/spark/pull/13001
[SPARK-15223] [DOCS] fix wrongly named config reference
## What changes were proposed in this pull request?
The configuration setting `spark.executor.logs.rolling.size.maxBytes` was
changed to `spark.executor.logs.rolling.maxSize` in 1.4 or so.
This commit fixes a remaining reference to the old name in the
documentation.
Also the description for `spark.executor.logs.rolling.maxSize` was edited
to clearly state that the unit for the size is bytes.
## How was this patch tested?
no tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/philipphoffmann/spark patch-3
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13001.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 #13001
----
commit 3cbec74690c88a219c15d3d504c75c36af92da73
Author: Philipp Hoffmann <[email protected]>
Date: 2016-05-09T09:34:07Z
[SPARK-15223] [DOCS] fix wrongly named reference to
spark.executor.logs.rolling.maxSize
The configuration setting `spark.executor.logs.rolling.size.maxBytes` was
changed to `spark.executor.logs.rolling.maxSize` in 1.4 or so.
This commit fixes a remaining reference to the old name in the
documentation.
Also the description for `spark.executor.logs.rolling.maxSize` was edited
to clearly state that the unit for the size is bytes.
----
---
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]
