dongjoon-hyun commented on pull request #28833:
URL: https://github.com/apache/spark/pull/28833#issuecomment-659086163
I guess we can forbid that too consistently as a continuation of this
approach.
BTW, until now, it's beyond of the scope because this PR was designed to
prevent Hive
dongjoon-hyun commented on pull request #28833:
URL: https://github.com/apache/spark/pull/28833#issuecomment-657383898
Hi, @ulysses-you . We already choose the plan. This is a step to forbid that
gracefully.
For `create view v1 as select null as col`, we can add an
`AnalysisException`
dongjoon-hyun commented on pull request #28833:
URL: https://github.com/apache/spark/pull/28833#issuecomment-655295006
Could you make a follow-up as what you suggest, @HyukjinKwon ?
This is an automated message from the
dongjoon-hyun commented on pull request #28833:
URL: https://github.com/apache/spark/pull/28833#issuecomment-655291242
First of all, it's not a good idea to add `NullType` into a new Spark
datatype officially. If that is an official type, what can we do in Spark SQL
world
dongjoon-hyun commented on pull request #28833:
URL: https://github.com/apache/spark/pull/28833#issuecomment-655234096
Merged to master. Thank you for your patience, @LantaoJin .
This is an automated message from the Apache
dongjoon-hyun commented on pull request #28833:
URL: https://github.com/apache/spark/pull/28833#issuecomment-653933187
Retest this please.
This is an automated message from the Apache Git Service.
To respond to the message,
dongjoon-hyun commented on pull request #28833:
URL: https://github.com/apache/spark/pull/28833#issuecomment-652239258
Does this close https://github.com/apache/spark/pull/28935 too?
This is an automated message from the
