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

gurwls223 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new 44d08cb97eff [MINOR][CONNECT] Fix missing request metadata in RPC call
44d08cb97eff is described below

commit 44d08cb97eff82550cf07297f4266f34e4a9146d
Author: Martin Grund <[email protected]>
AuthorDate: Wed Sep 11 20:13:32 2024 +0900

    [MINOR][CONNECT] Fix missing request metadata in RPC call
    
    ### What changes were proposed in this pull request?
    The RPC call for fetching the enriched error messages did not receive the 
GPRC channel per-request metadata, similar to all other other cases of calling 
the stub. This patch fixes this issue.
    
    ### Why are the changes needed?
    Compatibility
    
    ### Does this PR introduce _any_ user-facing change?
    No
    
    ### How was this patch tested?
    Existing tests.
    
    ### Was this patch authored or co-authored using generative AI tooling?
    No
    
    Closes #48070 from grundprinzip/minor_metadata.
    
    Authored-by: Martin Grund <[email protected]>
    Signed-off-by: Hyukjin Kwon <[email protected]>
---
 python/pyspark/sql/connect/client/core.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/python/pyspark/sql/connect/client/core.py 
b/python/pyspark/sql/connect/client/core.py
index 35dcf677fdb7..adba1b42a8bd 100644
--- a/python/pyspark/sql/connect/client/core.py
+++ b/python/pyspark/sql/connect/client/core.py
@@ -1786,7 +1786,7 @@ class SparkConnectClient(object):
             req.user_context.user_id = self._user_id
 
         try:
-            return self._stub.FetchErrorDetails(req)
+            return self._stub.FetchErrorDetails(req, 
metadata=self._builder.metadata())
         except grpc.RpcError:
             return None
 


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

Reply via email to