[
https://issues.apache.org/jira/browse/DERBY-5684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276733#comment-13276733 ]
Kristian Waagan commented on DERBY-5684:
----------------------------------------
DW>> What scenario corresponds to this latter case below (irg == null):?
KW> I don't remember... I'll remove irg == null and see if I added it because a test fell over (I think so, but maybe I had a bug somewhere else that caused this behavior).
I added the following code to the ConglomerateDescriptor constructor and ran suites.All (indexable and indexRowGenerator are both declared as final):
+ if (indexable && indexRowGenerator == null) {
+ throw new IllegalStateException("irg is null, indexable is true");
+ }
I didn't see any test failures, so my conclusion is that the check in IndexStatisticsAnalyzer can be dropped.
> Explore possible istat daemon improvements and optimizations
> ------------------------------------------------------------
>
> Key: DERBY-5684
> URL:
https://issues.apache.org/jira/browse/DERBY-5684> Project: Derby
> Issue Type: Task
> Reporter: Kristian Waagan
> Attachments: derby-istat-exploration-1.diff, derby-istat-exploration-2.diff, derby-istat-exploration.diff
>
>
> A task tracking some experiments on the istat daemon and the statistics update code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspaFor more information on JIRA, see:
http://www.atlassian.com/software/jira
