db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5164) Provide a framework to test upgrade between point releases. Currently, the upgrade testing happens between two major versions.
Date Wed, 01 Jun 2011 22:13:47 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mamta A. Satoor updated DERBY-5164:
-----------------------------------

    Attachment: derby5164_patch1_stat.txt
                derby5164_patch1_diff.txt

We want to do upgrade testing from 10.7.1.1 to 10.7 codeline because 10.7.1.1 had a data corruption
bug
DERBY-5121. 

The data corruption was caused by incorrect trigger action SPSes generated by Derby 10.7.1.1.
This was fixed in 10.7 codeline and future codelines by backing out code causing the corruption.
So 10.8 and onwards releases and the next 10.7 point release will have correct trigger action
SPSes. We want to test that the SPSes get fixed as part of upgrade from 10.7.1.1 to 10.7 codeline
and future Derby codelines. 

I have attached a patch derby5164_patch1_diff.txt for trunk to this jira which will provide
an upgrade mechanism from 10.7.1.1 to 10.7 codeline when the upgrade tests are being run in
10.7 codeline. In 10.8 and trunk codelines, we will not be testing upgrade from 10.7.1.1 to
10.7 (since it will be done through the 10.7 codeline upgrade testing) 

If anyone has any feedback on this patch, please let me know. If there are no comments, then
I will go ahead and commit this patch on Thursday evening and will work
on backporting it to 10.8 and 10.7 codeline. 

The backport to 10.8 will look the same as the changes suggested for trunk by the attached
patch.

The backport to 10.7 will have the flag UPGRADE_MINOR_7 in UpgradeRun.java set to true because
in 10.7 codeline, we do want to test the upgrade path from 10.7.1.1 to 10.7 codeline.

> Provide a framework to test upgrade between point releases. Currently, the upgrade testing
happens between two major versions.
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5164
>                 URL: https://issues.apache.org/jira/browse/DERBY-5164
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.0.2.1, 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.4.2.0, 10.5.3.0, 10.6.2.1,
10.7.1.1
>            Reporter: Mamta A. Satoor
>            Assignee: Mamta A. Satoor
>         Attachments: derby5164_patch1_diff.txt, derby5164_patch1_stat.txt
>
>
> DERBY-5121 found a corruption problem caused by triggers in DERBY release 10.7.1.1 A
fix for this has been provided in trunk(10.8) and the 10.7 codeline. 10.7.1.1 database upgrade
to any one of these 2 codelines will fix the triggers causing the corruption. I was able to
write upgrade tests for 10.8 codeline but not for 10.7 codeline. The reason for this can be
found in the comment insdie org.apache.derbyTesting.functionTests.tests.upgradeTests.UpgradeRun:baseSuite

>     * Changes are only added if the old version is older than
>     * then version the changes represent. Thus Changes10_2
>     * is not added if the old database (upgrade from) is already
>     * at 10.2, since Changes10_2 is intended to test upgrade
>     * from an older version to 10.2.
> The last line in the comment "since Changes10_2 is intended to test upgrade from an older
version to 10.2." is not really true specifically for DERBY-5121. We want to test upgrade
from 10.7.1.1 to next point release/codeline of 10.7.
> Providing this framework should not be too hard. I just wanted to create this jira so
we can keep track of the issue.
> More information on this issue can be found at http://mail-archives.apache.org/mod_mbox/db-derby-dev/201103.mbox/%3CAANLkTinYKkO0nef+8gM4oJmRE0jnzC-qbXy3ZN4_e3oG@mail.gmail.com%3E

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message