Github user eyalfa commented on the issue:

    https://github.com/apache/spark/pull/14444
  
    @hvanhovell , I'm currently trying your approach of testing `ne.resolved` 
prior to accessing `ne.name`.
    tests are running as I write here, but a quick dive into the 
`NamedExpression` hierarchy revealed some more cases (other than `Star`) where 
the names are not available prior to analysis, i.e.`UnresolvedAlias` and 
`MultiAlias`, there's also `UnresolvedAttribute` which isn't resolved but its 
name is always available (doesn't throw).
    even though I've tried I couldn't come up with a use case that combines 
these expressions with `CreateStruct`, I'd appreciate if any of you guys can 
shed some light on these classes, especially `UnresolvedAlias`. I'm a bit 
worried about this one as I suspect `CreateStruct.apply` might encounter one, 
looking at `Analyzer` shows that `ResolveAliases` is executed after 
`ResolveFunctions` so I guess my concern is at least theoretically possible. 


---
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

Reply via email to