[ 
https://issues.apache.org/jira/browse/SPARK-62128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated SPARK-62128:
-----------------------------------
    Labels: pull-request-available  (was: )

> Read a grpc-status-details-bin that is not valid base64 as grpcio does, of 
> the errors of grpc_status's from_call, in the Python client
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-62128
>                 URL: https://issues.apache.org/jira/browse/SPARK-62128
>             Project: Spark
>          Issue Type: Bug
>          Components: Connect
>    Affects Versions: 5.0.0
>            Reporter: Hyukjin Kwon
>            Priority: Major
>              Labels: pull-request-available
>
> After SPARK-62123, the Rust transport of the Python client 
> (pyspark-client-rust) refuses a response of a grpc-status-details-bin trailer 
> that is not valid base64, failing the call INTERNAL "Error parsing 
> 'grpc-status-details-bin' metadata: illegal base64 encoding", and takes 
> details that are base64 but not a google.rpc.Status as absent. grpcio, of 
> pyspark-client 4.3.0, refuses only other -bin keys of invalid base64: gRPC 
> core passes the details on, empty, so PySpark's rpc_status.from_call raises 
> "ValueError: Code in Status proto (StatusCode.OK) doesn't match status code 
> (StatusCode.INTERNAL)", and details that are not a Status raise protobuf's 
> "DecodeError: Error parsing message with type 'google.rpc.Status': Wire 
> format was corrupt".
> Expected: as grpcio and pyspark-client, for both unary and streaming calls. 
> Only a broken server sends such details.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

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

Reply via email to