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 c75d4aa  [SPARK-31269][DOC][FOLLOWUP][MINOR] Add version head of 
GraphX table
c75d4aa is described below

commit c75d4aa9c7b7c3a6a090b61ae82b2152d780eabb
Author: beliefer <[email protected]>
AuthorDate: Wed Apr 8 12:25:06 2020 +0900

    [SPARK-31269][DOC][FOLLOWUP][MINOR] Add version head of GraphX table
    
    ### What changes were proposed in this pull request?
    HyukjinKwon have ported back all the PR about version to branch-3.0.
    I make a double check and found GraphX table lost version head.
    This PR will fix the issue.
    HyukjinKwon, please help me merge this PR to master and branch-3.0
    
    ### Why are the changes needed?
    Add version head of GraphX table
    
    ### Does this PR introduce any user-facing change?
    'No'.
    
    ### How was this patch tested?
    Jenkins test.
    
    Closes #28149 from beliefer/fix-head-of-graphx-table.
    
    Authored-by: beliefer <[email protected]>
    Signed-off-by: HyukjinKwon <[email protected]>
    (cherry picked from commit 0fc859b4d56fc13bffa1937720d0a988bc7486ac)
    Signed-off-by: HyukjinKwon <[email protected]>
---
 docs/configuration.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/configuration.md b/docs/configuration.md
index fae3bb4..8e78ef2 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -2812,7 +2812,7 @@ Spark subsystems.
 ### GraphX
 
 <table class="table">
-<tr><th>Property Name</th><th>Default</th><th>Meaning</th></tr>
+<tr><th>Property Name</th><th>Default</th><th>Meaning</th><th>Since 
Version</th></tr>
 <tr>
   <td><code>spark.graphx.pregel.checkpointInterval</code></td>
   <td>-1</td>


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

Reply via email to