Github user avati commented on the pull request:
https://github.com/apache/spark/pull/1709#issuecomment-50923602
So, it looks like with:
a.withNullability (in
https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/dsl/package.scala#L199
)
type inference is selecting the type Attribute at
https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/namedExpressions.scala#L60
instead of AttributeReference at
https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/namedExpressions.scala#L137
Do you have a preference on how to make the code less ambiguous?
On Fri, Aug 1, 2014 at 11:41 AM, Michael Armbrust <[email protected]>
wrote:
> at should be added by this implicit conversion
>
<https://github.com/apache/spark/blob/master/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/dsl/package.scala#L205>
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/1709#issuecomment-50920007>.
>
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
