You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Junjie Peng (JIRA)" <ji...@apache.org> on 2008/08/11 16:31:46 UTC
[jira] Created: (DERBY-3831) RuntimeStatisticsParser can not
distinguish names of table or index well and truly
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: Tools
Reporter: Junjie Peng
Assignee: Junjie Peng
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.
Re: [jira] Created: (DERBY-3831) RuntimeStatisticsParser can not distinguish names of table or index well and truly
Posted by Junjie Peng <pj...@gmail.com>.
Oh, I've got it! Thanks, Dag. I have changed the issue fromToos to Test.
Ragards
Junjie
2008/8/19 Dag H. Wanvik <Da...@sun.com>
> Junjie Peng <pj...@gmail.com> writes:
>
> > Hi, Dag. I'm a little puzzled. RuntimeStatisticsParser is in the package
> > "org.apache.derbyTesting.junit". I think it is a tool for test, but not a
> > test itself.
>
> Yes it 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.
>
> Please see also
>
> http://db.apache.org/derby/binaries/FilingDerbyIssuesInJira.doc
>
> referenced from this wiki page:
> http://db.apache.org/derby/DerbyBugGuidelines.html
>
> Dag
>
>
>
> > Wish for your reply.
> >
> > Regards
> > Junjie
> >
> > 2008/8/19 Dag H. Wanvik <Da...@sun.com>
> >
> >> "Junjie Peng (JIRA)" <ji...@apache.org> writes:
> >>
> >> Is Tools the correct component for this issue? I would have thought it
> >> should be 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: Tools
> >> > Reporter: Junjie Peng
> >> > Assignee: Junjie Peng
> >> >
> >> >
> >> > 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.
> >> >
> >> >
> >> >
> >>
> >> --
> >> Dag H. Wanvik, staff engineer
> >> Sun Microsystems, Databases (JavaDB/Derby)
> >> Haakon VII gt. 7b, N-7485 Trondheim, Norway
> >> Tel: x43496/+47 73842196, Fax: +47 73842101
> >>
>
> --
> Dag H. Wanvik, staff engineer
> Sun Microsystems, Databases (JavaDB/Derby)
> Haakon VII gt. 7b, N-7485 Trondheim, Norway
> Tel: x43496/+47 73842196, Fax: +47 73842101
>
Re: [jira] Created: (DERBY-3831) RuntimeStatisticsParser can not
distinguish names of table or index well and truly
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
Junjie Peng <pj...@gmail.com> writes:
> Hi, Dag. I'm a little puzzled. RuntimeStatisticsParser is in the package
> "org.apache.derbyTesting.junit". I think it is a tool for test, but not a
> test itself.
Yes it 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.
Please see also
http://db.apache.org/derby/binaries/FilingDerbyIssuesInJira.doc
referenced from this wiki page:
http://db.apache.org/derby/DerbyBugGuidelines.html
Dag
> Wish for your reply.
>
> Regards
> Junjie
>
> 2008/8/19 Dag H. Wanvik <Da...@sun.com>
>
>> "Junjie Peng (JIRA)" <ji...@apache.org> writes:
>>
>> Is Tools the correct component for this issue? I would have thought it
>> should be 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: Tools
>> > Reporter: Junjie Peng
>> > Assignee: Junjie Peng
>> >
>> >
>> > 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.
>> >
>> >
>> >
>>
>> --
>> Dag H. Wanvik, staff engineer
>> Sun Microsystems, Databases (JavaDB/Derby)
>> Haakon VII gt. 7b, N-7485 Trondheim, Norway
>> Tel: x43496/+47 73842196, Fax: +47 73842101
>>
--
Dag H. Wanvik, staff engineer
Sun Microsystems, Databases (JavaDB/Derby)
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax: +47 73842101
Re: [jira] Created: (DERBY-3831) RuntimeStatisticsParser can not distinguish names of table or index well and truly
Posted by Junjie Peng <pj...@gmail.com>.
Hi, Dag. I'm a little puzzled. RuntimeStatisticsParser is in the package
"org.apache.derbyTesting.junit". I think it is a tool for test, but not a
test itself.
Wish for your reply.
Regards
Junjie
2008/8/19 Dag H. Wanvik <Da...@sun.com>
> "Junjie Peng (JIRA)" <ji...@apache.org> writes:
>
> Is Tools the correct component for this issue? I would have thought it
> should be 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: Tools
> > Reporter: Junjie Peng
> > Assignee: Junjie Peng
> >
> >
> > 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.
> >
> >
> >
>
> --
> Dag H. Wanvik, staff engineer
> Sun Microsystems, Databases (JavaDB/Derby)
> Haakon VII gt. 7b, N-7485 Trondheim, Norway
> Tel: x43496/+47 73842196, Fax: +47 73842101
>
Re: [jira] Created: (DERBY-3831) RuntimeStatisticsParser can not
distinguish names of table or index well and truly
Posted by "Dag H. Wanvik" <Da...@Sun.COM>.
"Junjie Peng (JIRA)" <ji...@apache.org> writes:
Is Tools the correct component for this issue? I would have thought it
should be 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: Tools
> Reporter: Junjie Peng
> Assignee: Junjie Peng
>
>
> 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.
>
>
>
--
Dag H. Wanvik, staff engineer
Sun Microsystems, Databases (JavaDB/Derby)
Haakon VII gt. 7b, N-7485 Trondheim, Norway
Tel: x43496/+47 73842196, Fax: +47 73842101
[jira] Closed: (DERBY-3831) RuntimeStatisticsParser can not
distinguish names of table or index well and truly
Posted by "Junjie Peng (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junjie Peng closed DERBY-3831.
------------------------------
Thank you, Myrna. It's much better.
> 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: Tools
> 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.
[jira] Updated: (DERBY-3831) RuntimeStatisticsParser can not
distinguish names of table or index well and truly
Posted by "Junjie Peng (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (DERBY-3831) RuntimeStatisticsParser can not
distinguish names of table or index well and truly
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Myrna van Lunteren resolved DERBY-3831.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.5.0.0
Derby Info: (was: [Patch Available])
This was a good find, thx...
However, when I ran the tests that use the modified methods in RuntimeStatisticsParser:
...lang.UpdateStatisticsTest
...lang.PredicatePushdownTest and the newly added
...lang.OptimizerOverridesTest
I got a failure in PredicatePushdownTest on the usedIndexRowToBaseRow method. The runtimestatistics output actually never shows a space in that line after the tablename, but a : (colon).
I modified that method to look for a colon after the table name and committed the change with revision 685733.
> 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: Tools
> 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.
[jira] Updated: (DERBY-3831) RuntimeStatisticsParser can not
distinguish names of table or index well and truly
Posted by "Junjie Peng (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junjie Peng updated DERBY-3831:
-------------------------------
Attachment: (was: derby-3831-1.stat)
> 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: Tools
> Reporter: Junjie Peng
> Assignee: Junjie Peng
> 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.
[jira] Updated: (DERBY-3831) RuntimeStatisticsParser can not
distinguish names of table or index well and truly
Posted by "Junjie Peng (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junjie Peng updated DERBY-3831:
-------------------------------
Attachment: derby-3831-1.stat
> 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: Tools
> Reporter: Junjie Peng
> Assignee: Junjie Peng
> 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.
[jira] Updated: (DERBY-3831) RuntimeStatisticsParser can not
distinguish names of table or index well and truly
Posted by "Junjie Peng (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-3831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Junjie Peng updated DERBY-3831:
-------------------------------
Attachment: derby-3831-1.patch
derby-3831-1.stat
> 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: Tools
> Reporter: Junjie Peng
> Assignee: Junjie Peng
> 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.