Mailing-List: contact dev-help@tajo.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tajo.incubator.apache.org
Date: Fri, 20 Sep 2013 14:59:51 +0000 (UTC)
From: "Hyunsik Choi (JIRA)" <jira@apache.org>
To: dev@tajo.incubator.apache.org
Message-ID: <JIRA.12668949.1379400892540.168196.1379689191656@arcas>
In-Reply-To: <JIRA.12668949.1379400892540@arcas>
References: <JIRA.12668949.1379400892540@arcas>
Subject: [jira] [Updated] (TAJO-187) The exception 'Some targets cannot be
 evaluated' is caused in nested joins
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/TAJO-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-187:
------------------------------

    Attachment: TAJO-187.patch

I've uploaded the patch. This bug was caused by the case sensitivity of relation names. In Tajo, relation names deal as lower case strings. But, TableSubQueryNode used relation names in case sensitive manner.

This patch depends on TAJO-46 and TAJO-186. You should sequentially apply the patch of TAJO-186 and TAJO-46 before applying this patch.
                
> The exception 'Some targets cannot be evaluated' is caused in nested joins
> --------------------------------------------------------------------------
>
>                 Key: TAJO-187
>                 URL: https://issues.apache.org/jira/browse/TAJO-187
>             Project: Tajo
>          Issue Type: Bug
>            Reporter: Seungun Choe
>            Assignee: Hyunsik Choi
>         Attachments: TAJO-187.patch
>
>
> {code}
> INSERT OVERWRITE into table1
> SELECT
>         B.num,
>         A.hash,
>         A.host,
>         A.hour,
>         A.date
> FROM
> (SELECT * FROM place WHERE host LIKE '%.google.com' AND date LIKE '201307%') A
> JOIN table2 B ON A.hash=B.hash
> {code}
> This query makes some error message.
>   - Some targets cannot be evaluated in the query block "@NONAME_1"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira