This is an automated email from the ASF dual-hosted git repository.

yao pushed a commit to branch branch-3.4
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/branch-3.4 by this push:
     new 22115214670d [SPARK-47172][DOCS][FOLLOWUP] Fix 
spark.network.crypto.ciphersince version field on security page
22115214670d is described below

commit 22115214670d76e11f37b36ac8a2a8aabcbd603d
Author: Kent Yao <[email protected]>
AuthorDate: Tue Jul 16 10:13:44 2024 +0800

    [SPARK-47172][DOCS][FOLLOWUP] Fix spark.network.crypto.ciphersince version 
field on security page
    
    ### What changes were proposed in this pull request?
    
    Given that SPARK-47172 was an improvement but got merged into 3.4/3.5, we 
need to fix the since version to eliminate misunderstandings.
    
    ### Why are the changes needed?
    
    doc fix
    
    ### Does this PR introduce _any_ user-facing change?
    
    no
    
    ### How was this patch tested?
    
    doc build
    
    ### Was this patch authored or co-authored using generative AI tooling?
    no
    
    Closes #47353 from yaooqinn/SPARK-47172.
    
    Authored-by: Kent Yao <[email protected]>
    Signed-off-by: Kent Yao <[email protected]>
    (cherry picked from commit d8820a07eb82acd35a1c9d4ff6ee4f65fc6aac29)
    Signed-off-by: Kent Yao <[email protected]>
---
 docs/security.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/security.md b/docs/security.md
index a9ae434e9d71..2c61a64c36a6 100644
--- a/docs/security.md
+++ b/docs/security.md
@@ -168,7 +168,7 @@ The following table describes the different options 
available for configuring th
     Cipher mode to use. Defaults "AES/CTR/NoPadding" for backward 
compatibility, which is not authenticated. 
     Recommended to use "AES/GCM/NoPadding", which is an authenticated 
encryption mode.
   </td>
-  <td>4.0.0</td>
+  <td>4.0.0, 3.5.2, 3.4.4</td>
 </tr>
 <tr>
   <td><code>spark.network.crypto.authEngineVersion</code></td>


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

Reply via email to