[jira] [Resolved] (TRAFODION-461) LP Bug: 1343642 - compiler: potential issue with ScanOptimizer::getNumActivePartitions

["Qifan Chen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TRAFODION-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Qifan Chen resolved TRAFODION-461.
----------------------------------
    Resolution: Fixed

A new data member FileScan::computedNumOfActivePartitions_ is added and populated during the FileScan construction, for  scan on range partitioned tables. 

The number of active partitions is defined as the number of partitions that will be scanned, after applying the search key. 

The method RangePartitioningFunction::computeNumOfActivePartitions() does the major work. 







> 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
>             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)