You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/08/22 02:01:09 UTC
[GitHub] [spark] cloud-fan commented on issue #25453: [SPARK-28730][SQL]
Configurable type coercion policy for table insertion
cloud-fan commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion policy for table insertion
URL: https://github.com/apache/spark/pull/25453#issuecomment-523715573
> Any thoughts on whether we can get rid of legacy mode for v1 if we implement ANSI mode?
The general policy is to keep the legacy config for at least one release, if a behavior change is made. I think we can remove it in 3.1.
I agree with forbidding legacy mode in v2. For now we can make v1 and v2 have different default policies. Once we make ANSI policy the default, then v1 and v2 can still have the same default policy.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org