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

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

Github user dongjoon-hyun commented on the pull request:

    https://github.com/apache/tajo/pull/442#issuecomment-90395916
  
    Hmm. Let me check for a second. I found the following Jenkins logs.
    ```
    [ERROR] COMPILATION ERROR : 
    [INFO] -------------------------------------------------------------
    [ERROR] 
/home/jenkins/jenkins-slave/workspace/PreCommit-TAJO-Build/incubator-tajo/tajo-core/src/main/java/org/apache/tajo/master/GlobalEngine.java:[160,13]
 
setQueryCache(com.google.common.cache.LoadingCache<java.lang.String,org.apache.tajo.algebra.Expr>)
 in org.apache.tajo.session.Session cannot be applied to 
(com.google.common.cache.LoadingCache<java.lang.Object,org.apache.tajo.algebra.Expr>)
    [INFO] 1 error
    ```


> Improve SQLAnalyzer by session-based parsing-result caching
> -----------------------------------------------------------
>
>                 Key: TAJO-1430
>                 URL: https://issues.apache.org/jira/browse/TAJO-1430
>             Project: Tajo
>          Issue Type: New Feature
>          Components: parser
>    Affects Versions: 0.10.0
>            Reporter: Dongjoon Hyun
>            Assignee: Dongjoon Hyun
>             Fix For: 0.10.1
>
>         Attachments: TAJO-1430.Hyun.150407.0.patch.txt, TAJO-1430.patch, 
> long_2times.sql, wide_table.sql
>
>
> There are wide tables with many many columns. Moveover, BI tools generate 
> very complex queries whose size is several MB. Although Tajo executes those 
> queries very fast in a few seconds, the total time of UX is slow.
> To become a fastest Hadoop DW, we need this following feature. 
> {code:sql}
> tsql -f long_2times.sql
> ...
> (0 rows, 30.641 sec, 0 B selected)
> ...
> (0 rows, 1.707 sec, 0 B selected)
> {code}



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

Reply via email to