You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Alice Chen (JIRA)" <ji...@apache.org> on 2015/07/22 20:15:43 UTC
[jira] [Created] (TRAFODION-346) LP Bug: 1326103 - Optimizer always
restricts HbaseScan DoP to number of nodes in cluster
Alice Chen created TRAFODION-346:
------------------------------------
Summary: LP Bug: 1326103 - Optimizer always restricts HbaseScan DoP to number of nodes in cluster
Key: TRAFODION-346
URL: https://issues.apache.org/jira/browse/TRAFODION-346
Project: Apache Trafodion
Issue Type: Bug
Components: sql-cmp
Reporter: Ravisha Neelakanthappa
Assignee: Ravisha Neelakanthappa
Priority: Critical
Fix For: 0.7 (pre-incubation)
The DoP is always restricted to number of Nodes for some plans. For example the plan produced by the optimizer for query
select * from shb1<<+ cardinality 10e6 >> is always:
>>explain options 'f' xx;
LC RC OP OPERATOR OPT DESCRIPTION CARD
---- ---- ---- -------------------- -------- -------------------- ---------
2 . 3 root 1.00E+000
1 . 2 esp_exchange 1:2(range) 1.00E+007
. . 1 trafodion_scan SHB1 1.00E+007
--- SQL operation complete.
setting parallel_num_esps and/or max_esps_per_cpu_per_op to increase the DoP didn't work. The table has 75 partitions and a big table. The default plan produced by the optimizer with DoP 2 is not an optimal one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)