[
https://issues.apache.org/jira/browse/DERBY-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972429#action_12972429
]
Knut Anders Hatlen commented on DERBY-4833:
-------------------------------------------
It sounds reasonable to wait and see if intermittent failures start appearing
in those test, and addressing all in one go if they do. Since the statistics
updates don't kick in unless the tables are above a certain minimum size, it
might not be a problem in most of those tests anyway.
> Prepare existing JUnit tests for running with automatic index statistics
> generation
> -----------------------------------------------------------------------------------
>
> Key: DERBY-4833
> URL: https://issues.apache.org/jira/browse/DERBY-4833
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.7.1.1
> Reporter: Kristian Waagan
> Assignee: Kristian Waagan
> Priority: Minor
> Attachments:
> derby-4833-1a-orderbyandsortavoidancetest_adjustment.diff,
> derby-4833-2a-updatelocks_disable_autostats.diff
>
>
> During prototyping of a mechanism to create and update index statistics
> automatically (see DERBY-4771) it turned out that some of the tests fail due
> to the presence of [improved] index statistics.
> Where appropriate the tests should be adjusted to cope with this background
> activity, and where not appropriate it should be noted such that the feature,
> when introduced, can be disabled.
> As part of this effort I will introduce a utility class for dealing with
> index statistics in tests. These will be used by some existing tests and also
> the new tests that will be written for the new feature.
> At this point two tests requiring adjustments have been identified
> (OrderByAndSortAvoidance, UpdateStatisticsTest), and one is under
> investigation (AutoIncrementTest). More may surface as the work on the
> feature progress.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
