[ http://issues.apache.org/jira/browse/DERBY-606?page=all ]
Mayuresh Nirhali updated DERBY-606:
-----------------------------------
Attachment: derby606_impl-v4.diff
derby606_upgrade-v4.diff
Thanks a lot suresh,
I think I misunderstood the proposal you gave initially about
CompressSpacePageOperation10_2 class. This new solution of having only 1 class
extending the old one to support old behavior seems to be the right thing to
do. I have done so, but the main class will need to have one extra check which
I could not avoid. Let me know if you have any workaround to this small nit in
the new approach.
I have also addressed your comments in this new set of patches. I have created
2 patches, one which includes implementation and test changes and another one
specifically for upgradeTest changes. Thanks for this tip.
I would really appreciate review comments on this.
> 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_upgrade-v4.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
