You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by gu...@apache.org on 2020/02/17 11:44:35 UTC
[spark] branch branch-3.0 updated: [SPARK-28869][DOCS][FOLLOWUP]
Add direct relationship between configs for rolling event log
This is an automated email from the ASF dual-hosted git repository.
gurwls223 pushed a commit to branch branch-3.0
in repository https://gitbox.apache.org/repos/asf/spark.git
The following commit(s) were added to refs/heads/branch-3.0 by this push:
new 7c09b57 [SPARK-28869][DOCS][FOLLOWUP] Add direct relationship between configs for rolling event log
7c09b57 is described below
commit 7c09b57355724c3330bab8e05c1c096ee487278d
Author: Jungtaek Lim (HeartSaVioR) <ka...@gmail.com>
AuthorDate: Mon Feb 17 20:41:56 2020 +0900
[SPARK-28869][DOCS][FOLLOWUP] Add direct relationship between configs for rolling event log
### What changes were proposed in this pull request?
This patch addresses the post-hoc review comment linked here - https://github.com/apache/spark/pull/25670#discussion_r373304076
### Why are the changes needed?
We would like to explicitly document the direct relationship before we finish up structuring of configurations.
### Does this PR introduce any user-facing change?
No.
### How was this patch tested?
N/A
Closes #27576 from HeartSaVioR/SPARK-28869-FOLLOWUP-doc.
Authored-by: Jungtaek Lim (HeartSaVioR) <ka...@gmail.com>
Signed-off-by: HyukjinKwon <gu...@apache.org>
(cherry picked from commit 446b2d2653a8ae0c9e35799eb4fc1d9f4dcd7991)
Signed-off-by: HyukjinKwon <gu...@apache.org>
---
core/src/main/scala/org/apache/spark/internal/config/package.scala | 5 +++--
docs/configuration.md | 2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/core/src/main/scala/org/apache/spark/internal/config/package.scala b/core/src/main/scala/org/apache/spark/internal/config/package.scala
index 02acb6b..652db2b 100644
--- a/core/src/main/scala/org/apache/spark/internal/config/package.scala
+++ b/core/src/main/scala/org/apache/spark/internal/config/package.scala
@@ -191,14 +191,15 @@ package object config {
private[spark] val EVENT_LOG_ENABLE_ROLLING =
ConfigBuilder("spark.eventLog.rolling.enabled")
- .doc("Whether rolling over event log files is enabled. If set to true, it cuts down " +
+ .doc("Whether rolling over event log files is enabled. If set to true, it cuts down " +
"each event log file to the configured size.")
.booleanConf
.createWithDefault(false)
private[spark] val EVENT_LOG_ROLLING_MAX_FILE_SIZE =
ConfigBuilder("spark.eventLog.rolling.maxFileSize")
- .doc("The max size of event log file to be rolled over.")
+ .doc(s"When ${EVENT_LOG_ENABLE_ROLLING.key}=true, specifies the max size of event log file" +
+ " to be rolled over.")
.bytesConf(ByteUnit.BYTE)
.checkValue(_ >= ByteUnit.MiB.toBytes(10), "Max file size of event log should be " +
"configured to be at least 10 MiB.")
diff --git a/docs/configuration.md b/docs/configuration.md
index 9c9cf84..6aafc91 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -1033,7 +1033,7 @@ Apart from these, the following properties are also available, and may be useful
<td><code>spark.eventLog.rolling.maxFileSize</code></td>
<td>128m</td>
<td>
- The max size of event log file before it's rolled over.
+ When <code>spark.eventLog.rolling.enabled=true</code>, specifies the max size of event log file before it's rolled over.
</td>
</tr>
<tr>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org