db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4833) Prepare existing JUnit tests for running with automatic index statistics generation
Date Mon, 13 Dec 2010 10:52:01 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970776#action_12970776
] 

Knut Anders Hatlen commented on DERBY-4833:
-------------------------------------------

Patch 2a looks fine to me. This is a problem that can happen in any test that checks the contents
of the lock table, isn't it? Do you think we'll need some systematic approach to handle this
problem, or would it be good enough to handle each occurrence on a case-by-case basis as they
show up? (With systematic approach I was thinking something like disabling automatic index
statistics update in every test that queries SYSCS_DIAG.LOCK_TABLE, or adding a procedure
that waits until the update thread's queue is empty, similar to T_Access.waitForPostCommitToFinish().)

> 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.


Mime
View raw message