[
https://issues.apache.org/jira/browse/DERBY-4771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lily Wei updated DERBY-4771:
----------------------------
Attachment: Derby-4771-2f-AutomaticIndexStatisticsTest_wondows7.rar
Thanks Kristian for all the detail information. I apply patch 2f. I clean the
build and run the AutomaticIndexStatisticsTest. As your prediction, take out
deleted deprecated properties make the hang go away. Yeah! Thank you! However,
I am still getting failure on testStatsCreatedOnGrowthThenDeleteDb,
testStatisticsCorrectness and testStatsCreatedOnGrowthThenDeleteDb. I am
including the .zip for my test result. I did not find a lot of tracing
information for index storage. Should this be the case?
It is great to learn we can drop table while statistic indexing daemon thread
is working. I think we can test it by turning feature on and run Suites.all. Is
that a right assumption? I did that and the tests run just fine.
> Continue investigation of automatic creation/update of index statistics
> -----------------------------------------------------------------------
>
> Key: DERBY-4771
> URL: https://issues.apache.org/jira/browse/DERBY-4771
> Project: Derby
> Issue Type: Task
> Components: SQL, Store
> Affects Versions: 10.8.0.0
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Attachments: autoindexstats.html,
> derby-4771-1a-prototype_code_dump.diff,
> derby-4771-1a-prototype_code_dump.stat,
> derby-4771-1b-prototype_code_dump.diff,
> derby-4771-2a-prototype_lcc_code_dump.diff,
> derby-4771-2b-prototype_lcc_code_dump.diff,
> derby-4771-2c-prototype_lcc_code_dump.diff,
> derby-4771-2d-prototype_lcc_code_dump.diff, DERBY-4771-2e-prototype.rar,
> derby-4771-2e-prototype_lcc_code_dump.diff,
> Derby-4771-2f-AutomaticIndexStatisticsTest_wondows7.rar,
> derby-4771-2f-prototype_lcc_code_dump-WORK-IN-PROGRESS.diff, derby.log,
> error-stacktrace.out, rjall.out, rjall.out, rjall.out, rjall.rar, rjone.out
>
>
> Work was started to improve Derby's handling of index statistics. This issue
> tracks further discussion and work for this task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
