rdblue commented on issue #25453: [SPARK-28730][SQL] Configurable type coercion 
policy for table insertion
URL: https://github.com/apache/spark/pull/25453#issuecomment-523541789
 
 
   If we want to have just one property, I think what we can do is use 
different defaults for v1 and v2, but use the same configuration property. That 
property should only support configuring ANSI and strict modes. That way, 
setting the property sets the same mode for v1 and v2, but doesn't allow v2 to 
use the unsafe legacy mode. v1 would continue to default to the legacy mode 
(unless we want to replace that with ANSI) and v2 would default to whatever is 
decided by the vote on the dev list.

----------------------------------------------------------------
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:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to