You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Qifan Chen (JIRA)" <ji...@apache.org> on 2015/10/05 18:14:27 UTC
[jira] [Commented] (TRAFODION-461) LP Bug: 1343642 - compiler:
potential issue with ScanOptimizer::getNumActivePartitions
[ https://issues.apache.org/jira/browse/TRAFODION-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943592#comment-14943592 ]
Qifan Chen commented on TRAFODION-461:
--------------------------------------
The level of the severity probably should be lowered to major, since Trafodion tables are accessed mostly either hash partitioned or single.
For range-partitied access of Trafodion or hive tables, yes a solution is very important.
> LP Bug: 1343642 - compiler: potential issue with ScanOptimizer::getNumActivePartitions
> --------------------------------------------------------------------------------------
>
> Key: TRAFODION-461
> URL: https://issues.apache.org/jira/browse/TRAFODION-461
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-cmp
> Reporter: Ravisha Neelakanthappa
> Assignee: Qifan Chen
> Priority: Critical
> Fix For: 2.0-incubating
>
>
> The function ScanOptimizer::getNumActivePartitions() is supposed to return how many partitions are going to accessed at runtime.
> This involves analyzing search key predicates and table partitions type (range or hash) so on. For example if the predicate is on key col like primary_key = <some existing col value>, this function should returns 1 active partition.
> Fixing this function to return correct number of partitions is important for Trafodion because we deal with range partitions in HBase.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)