[
https://issues.apache.org/jira/browse/DERBY-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029981#comment-13029981
]
Rick Hillegas commented on DERBY-5195:
--------------------------------------
Hi Kathey,
I agree that it would help tech support if we checked in DataFileReader,
ControlFileReader, and LogFileReader. Together they weigh a little under 60K so
I don't think we would significantly bloat up the engine jar if we checked them
into an engine directory. Maybe org.apache.derby.impl.store.tools? Mike may
have some better theory about where to put these tools.
Productizing these tools would be a little chunk of work:
1) Refactor the tools so that they share helper code which is currently
duplicated across them.
2) Wire them into the list of extra classes so that the jar builder puts them
into derby.jar.
3) Write regression tests to verify their behavior.
4) Document them in the Tools Guide.
Thanks,
-Rick
> Create tools for browsing the files in the database log directory.
> ------------------------------------------------------------------
>
> Key: DERBY-5195
> URL: https://issues.apache.org/jira/browse/DERBY-5195
> Project: Derby
> Issue Type: Task
> Affects Versions: 10.9.0.0
> Reporter: Rick Hillegas
> Attachments: ControlFileReader.java, ControlFileReader.java,
> LogFileReader.java, LogFileReader.java, LogFileReader.java
>
>
> It would be nice to have some tools to examine the contents of the log
> directory. The tools should be able to read the files in that directory
> without disturbing them.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira