You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/12/13 23:23:46 UTC

[jira] [Commented] (TAJO-2007) By default, Optimizer should use the table volume in TableStat.

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

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

Github user hyunsik commented on the pull request:

    https://github.com/apache/tajo/pull/900#issuecomment-164305715
  
    I rebased and fixed all tests. It is ready to review.


> By default, Optimizer should use the table volume in TableStat.
> ---------------------------------------------------------------
>
>                 Key: TAJO-2007
>                 URL: https://issues.apache.org/jira/browse/TAJO-2007
>             Project: Tajo
>          Issue Type: Improvement
>          Components: Planner/Optimizer
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.12.0, 0.11.1
>
>
> Currently, the optimizer by default gets table volumes through storage manager and employ them for join optimization. But, in some cases, it causes performance degradation because aggregating all file volumes is not cheap in large partitioned tables on S3 or HDFS.
> So, this patch improves TableStatUpdateRewriter to use table volumes of TableStat by default, and it also adds a session variable 'USE_TABLE_VOLUME' to allow the optimizer to use the table volume through storage handler.



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