Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/11822#issuecomment-198318534
Personally, I had once been quite confused by the fact that
`NamedExpression.qualifiers` is a `Seq[String]` and thought that attributes can
be qualified with multiple qualifiers like `db.table.column`. That's why
current version of `AttributeReference.sql` joins all qualifiers using `.`
rather than picking the first one.
I believe it's safe and good to enforce the at-most-one-qualifier
constraint at type level unless there do exist valid cases where using multiple
qualifiers makes sense but haven't been implemented in Spark SQL yet.
cc @marmbrus @rxin @yhuai
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
