[
https://issues.apache.org/jira/browse/TAJO-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15055561#comment-15055561
]
ASF GitHub Bot commented on TAJO-2007:
--------------------------------------
Github user jihoonson commented on a diff in the pull request:
https://github.com/apache/tajo/pull/900#discussion_r47466835
--- Diff:
tajo-core-tests/src/test/resources/results/TestCrossJoin/testCrossJoinOfOneSmallTableAndJoin.1.Sort.plan
---
@@ -37,21 +37,90 @@ Execution Block Graph (TERMINAL -
eb_0000000000000_0000_000008)
-------------------------------------------------------------------------------
|-eb_0000000000000_0000_000008
|-eb_0000000000000_0000_000007
+ |-eb_0000000000000_0000_000004
--- End diff --
This test should not be changed because it tests broadcast join.
> 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)
