[
https://issues.apache.org/jira/browse/TAJO-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14377527#comment-14377527
]
ASF GitHub Bot commented on TAJO-1430:
--------------------------------------
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/tajo/pull/442#issuecomment-85409177
The cache is maintained by approximately LRU manner with 200 size and also
cached item will be expired after 1 hour since last access.
'''
session.setQueryCache(CacheBuilder.newBuilder()
.maximumSize(200)
.expireAfterAccess(1, TimeUnit.HOURS)
.build(new CacheLoader<String, Expr>() {
public Expr load(String sql) throws SQLSyntaxError {
return analyzer.parse(sql);
}
})
);
'''
> Improve SQLAnalyzer by 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: 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)
