[
https://issues.apache.org/jira/browse/TAJO-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14372400#comment-14372400
]
Hyunsik Choi edited comment on TAJO-1430 at 3/21/15 12:46 AM:
--------------------------------------------------------------
Hi [~dongjoon],
Thank you for creating the jira issues. Actually, that work is very necessary.
I also think the change scope of improved PreparedStatement is somewhat vast.
So, they should be done in another jira, I think.
Anyway, this work with some cache invalidation method looks good. I also think
that Session would be a good place to cache the parsed result. it would be more
safe in many aspects.
Are umbrella issues about PreparedStatement or your project? If you meant
latter, you don't need to mention your project later. It would be easy to be
misunderstood. If the works are reasonable in Tajo, please just do it.
was (Author: hyunsik):
Hi [~dongjoon],
Thank you for creating the jira issues. Actually, that work is very necessary.
I also think the change scope of improved PreparedStatement is somewhat vast.
So, they should be done in another jira, I think.
Anyway, this work with some cache invalidation method looks good. I also think
that Session would be a good place to cache the parsed result. it would be more
safe in many aspects.
Are umbrella issues about PreparedStatement or your project? If you meant
latter, you don't need to mention your project. It would be easy to be
misunderstood. If the works are reasonable in Tajo, please just do it.
> 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: TAJO-1430.patch, long.sql, middle.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}
> time tsql -f middle.sql > /dev/null
> real 0m19.058s
> user 0m2.148s
> sys 0m0.268s
> time tsql -f ~/tajo/middle.sql > /dev/null
> real 0m18.496s
> user 0m2.119s
> sys 0m0.240s
> $ time ./tsql -f ~/tajo/long.sql > /dev/null
> real 0m36.974s
> user 0m2.305s
> sys 0m0.272s
> $ time ./tsql -f ~/tajo/long.sql > /dev/null
> real 0m4.103s
> user 0m2.237s
> sys 0m0.249s
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
