You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "V.Narayanan (JIRA)" <ji...@apache.org> on 2008/04/01 07:28:26 UTC
[jira] Commented: (DERBY-3552) Handle jar files that are installed
when replication is enabled
[ https://issues.apache.org/jira/browse/DERBY-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584011#action_12584011 ]
V.Narayanan commented on DERBY-3552:
------------------------------------
Kim says
>Why would you need to do a replace, or a remove/install, on the slave? If the jars are not installed on the slave,
>I would think you would just do an install.
Narayanan says (in an earlier comment)
>This would mean that allowing jar file operations during deletion would result
>in the system catalog table on the slave having a reference to the jar file that
>does not exist in the replicated database
So even if you do not do an install the derby system will assume the jar to be present and calling
a function that depends on the jar would result in (from an earlier run posted in the comments)
>ij> values myInc (5,10);
>ERROR 42X51: The class 'MyMathFuncs' does not exist or is inaccessible. This can happen if the class is not public.
>ERROR XJ001: Java exception: 'MyMathFuncs: java.lang.ClassNotFoundException'.
Hence you need to replace, remove/install to modify the earlier system catalog entry for that jar.
> Handle jar files that are installed when replication is enabled
> ---------------------------------------------------------------
>
> Key: DERBY-3552
> URL: https://issues.apache.org/jira/browse/DERBY-3552
> Project: Derby
> Issue Type: Sub-task
> Components: Replication
> Affects Versions: 10.4.0.0, 10.5.0.0
> Reporter: V.Narayanan
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.