[
https://issues.apache.org/jira/browse/DERBY-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
V.Narayanan updated DERBY-3064:
-------------------------------
Attachment: LogShipperIntegration_v3.stat
LogShipperIntegration_v3.diff
In this patch
* I have addressed the issues pointed out with respect to logging
in the MasterController.
* I have followed the same pattern as in SlaveController in extending
the ReplicationLogger and using the logError method. I however thought
it would have been better to have had logError as a static method in the
ReplicationLogger class rather than extending the class into the controllers.
I decided not to disturb the structure of the classes for now.
I have not run tests on the patch. I shall run the tests and shall revert back.
> Implement the LogShipper that will enable the shipping of Log records from
> the master to the slave
> --------------------------------------------------------------------------------------------------
>
> Key: DERBY-3064
> URL: https://issues.apache.org/jira/browse/DERBY-3064
> Project: Derby
> Issue Type: Sub-task
> Components: Miscellaneous
> Reporter: V.Narayanan
> Assignee: V.Narayanan
> Attachments: LogShipperImpl_v1.diff, LogShipperImpl_v1.stat,
> LogShipperImpl_v2.diff, LogShipperImpl_v2.stat, LogShipperImpl_v3.diff,
> LogShipperImpl_v3.stat, LogShipperImpl_v4.diff, LogShipperImpl_v4.stat,
> LogShipperImpl_v5.diff, LogShipperImpl_v5.stat,
> LogShipperIntegration_v1.diff, LogShipperIntegration_v1.stat,
> LogShipperIntegration_v2.diff, LogShipperIntegration_v2.stat,
> LogShipperIntegration_v3.diff, LogShipperIntegration_v3.stat
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
