You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Alex Khakhlyuk (Jira)" <ji...@apache.org> on 2026/02/05 12:08:00 UTC
[jira] [Updated] (SPARK-55373) Improve noHandlerFoundForExtension error message
[ https://issues.apache.org/jira/browse/SPARK-55373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Khakhlyuk updated SPARK-55373:
-----------------------------------
Description:
Currently, Spark Connect Planner supports extension fields for Relation, Command, Expression protos. Extensions are processed through handlers. If a handler is not available for a given extension type, the planner will throw this error:
{code:java}
org.apache.spark.sql.connect.common.InvalidPlanInput: [INTERNAL_ERROR] No handler found for extension SQLSTATE: XX000 {code}
This error is not informative enough when debugging. I propose adding extension proto type url to the error message which will make it clear which extension is missing
{code:java}
org.apache.spark.sql.connect.common.InvalidPlanInput: [INTERNAL_ERROR] No handler found for extension type: type.googleapis.com/google.protobuf.StringValue SQLSTATE: XX000 {code}
was:
Currently, Spark Connect Planner supports extension fields for Relation, Command, Expression protos. Extensions are processed through handlers. If a handler is not available for a given extension type, the planner will throw this error:
{code:java}
org.apache.spark.sql.connect.common.InvalidPlanInput: [INTERNAL_ERROR] No handler found for extension SQLSTATE: XX000 {code}
This error is not informative enough when debugging. I propose adding extension proto type url to the error message which will make it clear which extension is missing
{code:java}
org.apache.spark.sql.connect.common.InvalidPlanInput: [INTERNAL_ERROR] No handler found for extension type: type.googleapis.com/spark.connect.SubscribeToLiveQuery SQLSTATE: XX000 {code}
> Improve noHandlerFoundForExtension error message
> ------------------------------------------------
>
> Key: SPARK-55373
> URL: https://issues.apache.org/jira/browse/SPARK-55373
> Project: Spark
> Issue Type: Bug
> Components: Connect
> Affects Versions: 4.1.1
> Reporter: Alex Khakhlyuk
> Priority: Major
>
> Currently, Spark Connect Planner supports extension fields for Relation, Command, Expression protos. Extensions are processed through handlers. If a handler is not available for a given extension type, the planner will throw this error:
> {code:java}
> org.apache.spark.sql.connect.common.InvalidPlanInput: [INTERNAL_ERROR] No handler found for extension SQLSTATE: XX000 {code}
> This error is not informative enough when debugging. I propose adding extension proto type url to the error message which will make it clear which extension is missing
> {code:java}
> org.apache.spark.sql.connect.common.InvalidPlanInput: [INTERNAL_ERROR] No handler found for extension type: type.googleapis.com/google.protobuf.StringValue SQLSTATE: XX000 {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org