[
https://issues.apache.org/jira/browse/SPARK-47429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17842694#comment-17842694
]
Nicholas Chammas commented on SPARK-47429:
------------------------------------------
I think one intermediate step we can take here is to mark the existing fields
as deprecated, indicating that they will be renamed. That way, if we don't
complete this renaming before the 4.0 release we at least have the deprecation
in.
Another thing we can do in addition to deprecating the existing fields is to
add the renamed fields and simply have them redirect to the original ones.
I will build a list of the classes, class attributes, methods, and method
parameters that will need this kind of update. Note that this list will be
much, much smaller than the thousands of uses that BingKun highlighted, since I
am just focusing on the declarations.
cc [~cloud_fan]
> Rename errorClass to errorCondition and subClass to subCondition
> ----------------------------------------------------------------
>
> Key: SPARK-47429
> URL: https://issues.apache.org/jira/browse/SPARK-47429
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 4.0.0
> Reporter: Nicholas Chammas
> Priority: Minor
> Attachments: image-2024-04-18-09-26-04-493.png
>
>
> We've agreed on the parent task to rename {{errorClass}} to align it more
> closely with the SQL standard, and take advantage of the opportunity to break
> backwards compatibility offered by the Spark version change from 3.5 to 4.0.
> This ticket also covers renaming {{subClass}} as well.
> This is a subtask so the changes are in their own PR and easier to review
> apart from other things.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
