[
https://issues.apache.org/jira/browse/DERBY-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Junjie Peng updated DERBY-3831:
-------------------------------
Component/s: (was: Tools)
Test
Derby Info: [Patch Available]
As Dag directed out, "RuntimeStatisticsParser is part of the testing
infrastructure. I think we use the test
category for that, cf. this file (RuntimeStatisticsParser.java) was
originally created by JIRA DERBY-2463 which is labelled with Category
Test. The tools category is reserved for the runnable tools like ij,
sysinfo, dblook and some utilities like install_jar, export and
import." So, change its components from Toos to Test.
> RuntimeStatisticsParser can not distinguish names of table or index well and
> truly
> ----------------------------------------------------------------------------------
>
> Key: DERBY-3831
> URL: https://issues.apache.org/jira/browse/DERBY-3831
> Project: Derby
> Issue Type: Bug
> Components: Test
> Reporter: Junjie Peng
> Assignee: Junjie Peng
> Fix For: 10.5.0.0
>
> Attachments: derby-3831-1.patch, derby-3831-1.stat
>
>
> RuntimeStatisticsParser can not distinguish names of table or index well and
> truly.
> i.e. there are two indexes t1_c1c2 and t1_c1 on table t1. Execute "select *
> from t1 --DeRbY-pRoPeRtIeS index = t1_c1c2" on t1.
> Then,RuntimeStatisticsParser.usedSpecificIndexForIndexScan("T1","T1_C1C2")
> will return true, while
> RuntimeStatisticsParser.usedSpecificIndexForIndexScan("T1","T1_C1") will
> return true too. It's not correct.
> The similar errors also exist on usedIndexScan(), usedIndexRowToBaseRow(),
> usedDistinctScan() and usedTableScan() in the class of
> RuntimeStatisticsParser.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
