Mailing-List: contact reviews-help@spark.apache.org; run by ezmlm
Precedence: bulk
From: cloud-fan <git@git.apache.org>
To: reviews@spark.apache.org
Reply-To: reviews@spark.apache.org
References: <git-pr-2542-spark@git.apache.org>
In-Reply-To: <git-pr-2542-spark@git.apache.org>
Subject: [GitHub] spark pull request: [SPARK-3688][SQL]LogicalPlan can't
 resolve col...
Content-Type: text/plain
Message-Id: <20141008102633.ABA8A9231D8@tyr.zones.apache.org>
Date: Wed,  8 Oct 2014 10:26:33 +0000 (UTC)

Github user cloud-fan commented on the pull request:

    https://github.com/apache/spark/pull/2542#issuecomment-58338302
  
    I tried this on hive:
    
        CREATE TABLE t1(x INT);
        CREATE TABLE t2(a STRUCT<x: INT>, k INT);
        SELECT a.x FROM t1 a JOIN t2 b;
    And hive can resolve this. However it is reasonable to report "ambiguous references" here, should we follow hive for this case?


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org