[GitHub] [spark] gengliangwang commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion policy for table insertion

gengliangwang commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion policy for table insertion URL: https://github.com/apache/spark/pull/25453#issuecomment-523557558 > If we want to have just one property, I think what we can do is use different defaults for v1 and v2, b

[GitHub] [spark] gengliangwang commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion policy for table insertion

gengliangwang commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion policy for table insertion URL: https://github.com/apache/spark/pull/25453#issuecomment-523329260 retest this please. This is an automated

[GitHub] [spark] gengliangwang commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion policy for table insertion

gengliangwang commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion policy for table insertion URL: https://github.com/apache/spark/pull/25453#issuecomment-523297016 > Why is that? We know that v2 already introduces breaking behavior changes and we can't avoid them. We w

[GitHub] [spark] gengliangwang commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion policy for table insertion

gengliangwang commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion policy for table insertion URL: https://github.com/apache/spark/pull/25453#issuecomment-521232172 CC @cloud-fan @maropu @rdblue @HyukjinKwon @mccheah If this is OK to you, I will apply the optional "s