[ 
https://issues.apache.org/jira/browse/TAJO-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14374982#comment-14374982
 ] 

ASF GitHub Bot commented on TAJO-1403:
--------------------------------------

Github user dongjoon-hyun commented on the pull request:

    https://github.com/apache/tajo/pull/434#issuecomment-84625233
  
    You're right, but when I can construct prefix from the subset of partition 
column, this patch handle that as a simple query. 
    /table_name/year=x/day=y/hour=z  (full path is simple query)
    /table_name/year=x/day=y               (prefix path is constructed, so 
simple query)
    /table_name/          /day=y/hour=z  (year is unknown, this is not simple 
query. It will be handled in an old fashion)
    /table_name/year=x/         /hour=z  (day is unknown, this is not simple 
query, too.) 


> Improve 'Simple Query' with only partition columns and constant values
> ----------------------------------------------------------------------
>
>                 Key: TAJO-1403
>                 URL: https://issues.apache.org/jira/browse/TAJO-1403
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: Dongjoon Hyun
>            Assignee: Dongjoon Hyun
>             Fix For: 0.11.0
>
>         Attachments: TAJO-1403.patch
>
>
> Tajo shows a very fast response for a simple query ( 
> https://cwiki.apache.org/confluence/display/TAJO/Simple+Query+and+Forwarded+Query)
>  like the followings.
> {code:sql}
> select * from t1 limit 10;
> {code}
> However, in many cases, tables have partitions. 
> {code:sql}
> create external table t1(id int) using csv with ('csvfile.delimiter'='|') 
> partition by column(dt text) location '/data';
> select * from t1 where dt='2015-03-15' limit 10;
> {code}
> If all predicates in WHERE consist of partition columns and 'EQUAL' 
> predicates with constant values, I think Tajo can handle these cases very 
> fast. 
> This kind of queries is very popular for DevOps users and simple ETL apps.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to