Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <17220215.1165514063044.JavaMail.jira@brutus>
Date: Thu, 7 Dec 2006 09:54:23 -0800 (PST)
From: "Mayuresh Nirhali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-606) SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE
 fails on (very) large tables
In-Reply-To: <867707277.1128640130796.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-606?page=all ]

Mayuresh Nirhali updated DERBY-606:
-----------------------------------

    Attachment: derby606_upgrade-v6.diff

> As Bryan and others pointed out Derby supports upgrade from 10.1 to 10.3
> also. This patch seems to incorrectly remove 10.1 to 10.3 upgrade test.

I considered this. The current framework for upgrade testing needs some modification to support upgrade from more than 1 prev releases. build.xml should create <test>_app.properties file for each such test in the upgradeSuite. Also, upgrade from 10.0 to 10.3 should be considered.  I looked into 10.2 and 10.1 workspaces and they contain only one test. One good thing is that, as mentioned in my other comments, UpgradeTester still includes all the testcases for upgrade from 10.0 and 10.1, so this work can be used to make upgradetest support upgrade from 10.0 and 10.1 to 10.3.

In my opinion, all This is probably out of scope for this bug. I feel, A follow up patch tracked by different JIRA entry can handle this effort. It might be useful to comment out the lines instead of removing, I shall do that. Please let me know what do you think.

------------------

Attached is another patch for upgrade tests. I simplified the 606 case to call compress for common scenario where old log record is used, instead of exercising the bug case. This case in Upgrade testing framework will also work with old/new releases and not just the combination of 10.2-10.3.


Thanks for your help !!
-- Mayuresh


> SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails on (very) large tables
> --------------------------------------------------------------------
>
>                 Key: DERBY-606
>                 URL: http://issues.apache.org/jira/browse/DERBY-606
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.1.1.0
>         Environment: Java 1.5.0_04 on Windows Server 2003 Web Edition
>            Reporter: Jeffrey Aguilera
>         Assigned To: Mayuresh Nirhali
>             Fix For: 10.3.0.0
>
>         Attachments: A606Test.java, derby606-v2.diff, derby606-v3.diff, derby606_impl-v4.diff, derby606_impl-v5.diff, derby606_impl-v6.diff, derby606_upgrade-v4.diff, derby606_upgrade-v5.diff, derby606_upgrade-v6.diff, derby606_v1.diff
>
>
> SYSCS_UTIL.SYSCS_INPLACE_COMPRESS_TABLE fails with one of the following error messages when applied to a very large table (>2GB):
> Log operation null encounters error writing itself out to the log stream, this could be caused by an errant log operation or internal log buffer full due to excessively large log operation. SQLSTATE: XJ001: Java exception: ': java.io.IOException'.
> or
> The exception 'java.lang.ArrayIndexOutOfBoundsException' was thrown while evaluating an expression. SQLSTATE: XJ001: Java exception: ': java.lang.ArrayIndexOutOfBoundsException'.
> In either case, no entry is written to the console log or to derby.log.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira