[
https://issues.apache.org/jira/browse/DERBY-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890731#action_12890731
]
Bryan Pendleton commented on DERBY-1958:
----------------------------------------
What do you think about adding a toString() method to RAFContainer? Then
instead of getting
Container org.apache.derby.impl.store.raw.data.rafcontai...@1318b
the message might contain something like:
Container (seg=1,ctr=113) version=4, estRows=104679 estPages=645 file=ca1.dat
inBackup=false
The best way to do this is probably to put toString() methods on BaseContainer,
FileContainer, and RAFContainer, and make sure that each toString() method
invokes super.toString() as part of its processing, since the printable
information
about a container is contained in classes up and down the hierarchy.
Mike can probably help us decide what information is most important to
include in the toString method so that the container state will be preserved in
the error message, but you could start by just looking at the member fields
of each of the classes and including them in the message.
>From a quick scan, I suspect that the most important fields to include in the
toString are:
- BaseContainer.identity
- FileContainer.pageSize
- FileContainer.containerVersion
- FileContainer.estimatedRowCount
- FileContainer.estimatedPageCount
- FileContainer.isDirty
- RAFContainer.fileData
- RAFContainer.actionCode
- RAFContainer.inBackup
- RAFContainer.inRemove
> improve XSDG3 error to print container, actual i/o operation, and file name.
> ----------------------------------------------------------------------------
>
> Key: DERBY-1958
> URL: https://issues.apache.org/jira/browse/DERBY-1958
> Project: Derby
> Issue Type: Improvement
> Components: Store
> Affects Versions: 10.1.3.1, 10.2.1.6, 10.3.1.4
> Reporter: Mike Matrigali
> Priority: Trivial
> Attachments: Derby-1958.diff
>
>
> The current error does not give enough information to know what container is
> the problem:
> ERROR XSDG3: Meta-data for Container
> org.apache.derby.impl.store.raw.data.rafcontai...@10632cd could not be
> accessed
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
