[
https://issues.apache.org/jira/browse/TAJO-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884035#comment-13884035
]
Jaehwa Jung edited comment on TAJO-558 at 1/28/14 11:30 AM:
------------------------------------------------------------
For reference, tajo didn't recognize it beforehand because there was no test
cases which were working under similar conditions. So, I'm going to add test
cases to verify physical operators based on HCatalogStore.
was (Author: blrunner):
For reference, tajo didn't recognize it beforehand because there was no test
cases. So, I'm going to add test cases to verify physical operators based on
HCatalogStore.
> HCatalogStore can't scan columns.
> ---------------------------------
>
> Key: TAJO-558
> URL: https://issues.apache.org/jira/browse/TAJO-558
> Project: Tajo
> Issue Type: Bug
> Components: catalog
> Affects Versions: 0.8-incubating
> Reporter: Jaehwa Jung
> Assignee: Jaehwa Jung
> Fix For: 0.8-incubating
>
>
> If we write partitioned columns at where clause on tsql, tajo print a error
> message as follows:
> {code:xml}
> tajo> select * from table1 where id = 1;
> ERROR: no such a column name default
> {code}
> For reference, hive table schema is as the following:
> {code:xml}
> CREATE TABLE table1(
> id int,
> name string,
> score float,
> type string);
> {code}
> It occurred on both managed tables and partitioned tables.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
