[GitHub] [spark] brkyvz commented on issue #27391: [SPARK-30612][SQL] Resolve qualified column name with v2 tables

2020-02-06 Thread GitBox
brkyvz commented on issue #27391: [SPARK-30612][SQL] Resolve qualified column name with v2 tables URL: https://github.com/apache/spark/pull/27391#issuecomment-583026619 Thanks @imback82 and @cloud-fan! This is an automated me

[GitHub] [spark] brkyvz commented on issue #27391: [SPARK-30612][SQL] Resolve qualified column name with v2 tables

2020-02-02 Thread GitBox
brkyvz commented on issue #27391: [SPARK-30612][SQL] Resolve qualified column name with v2 tables URL: https://github.com/apache/spark/pull/27391#issuecomment-581237957 Agree with @cloud-fan. Please do not remove the old code in resolution for the following too reasons: 1. It's very ri

[GitHub] [spark] brkyvz commented on issue #27391: [SPARK-30612][SQL] Resolve qualified column name with v2 tables

2020-01-30 Thread GitBox
brkyvz commented on issue #27391: [SPARK-30612][SQL] Resolve qualified column name with v2 tables URL: https://github.com/apache/spark/pull/27391#issuecomment-580521979 I don't think so for ALTER TABLE. You don't have any ambiguity there with respect to columns, therefore wouldn't need t