[
https://issues.apache.org/jira/browse/SPARK-30612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022675#comment-17022675
]
Terry Kim commented on SPARK-30612:
-----------------------------------
Thanks [~brkyvz]
There are two approaches we can take. One is to wrap v2 table with
`SubqueryAlias`. Another is to update `DataSourceV2Relation`'s output
(Seq[AttributeReference]) to have qualifier directly (after SPARK-30314). Which
route should I take?
> can't resolve qualified column name with v2 tables
> --------------------------------------------------
>
> Key: SPARK-30612
> URL: https://issues.apache.org/jira/browse/SPARK-30612
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Wenchen Fan
> Priority: Major
>
> When running queries with qualified columns like `SELECT t.a FROM t`, it
> fails to resolve for v2 tables.
> v1 table is fine as we always wrap the v1 relation with a `SubqueryAlias`. We
> should do the same for v2 tables.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
