[
https://issues.apache.org/jira/browse/TAJO-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15061573#comment-15061573
]
ASF GitHub Bot commented on TAJO-2007:
--------------------------------------
Github user hyunsik commented on the pull request:
https://github.com/apache/tajo/pull/900#issuecomment-165352379
@jihoonson Thank you for your comments. As we discussed in an offline, it
may be hard to handle the problem in this issue. Instead, I just created the
another jira [1] and add ``FIXME`` tags in the unit tests. We can resolve this
problem after we introduce hints.
[1] https://issues.apache.org/jira/browse/TAJO-2026
> 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)
