You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2020/02/17 17:05:00 UTC
[jira] [Resolved] (SPARK-30829) Define LegacyBehaviorPolicy
enumeration as the common value for result change configs
[ https://issues.apache.org/jira/browse/SPARK-30829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-30829.
---------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Issue resolved by pull request 27579
[https://github.com/apache/spark/pull/27579]
> Define LegacyBehaviorPolicy enumeration as the common value for result change configs
> -------------------------------------------------------------------------------------
>
> Key: SPARK-30829
> URL: https://issues.apache.org/jira/browse/SPARK-30829
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Yuanjian Li
> Assignee: Yuanjian Li
> Priority: Major
> Fix For: 3.0.0
>
>
> During API auditing for the 3.0 release, we found several new approaches that will change the results silently. For these features, we create a common config value, which is a three-value enumeration. Whenever the new behavior will silently change the results, this config can be reused.
> * Exception(default): Spark will throw an exception while result changes will happen, and remind users to choose between legacy and new behavior.
> * New Behavior: Use the new approach.
> * Legacy: Use the legacy behavior of earlier versions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org