db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "V.Narayanan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3169) Add documentation for replication
Date Wed, 19 Mar 2008 16:10:29 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580430#action_12580430
] 

V.Narayanan commented on DERBY-3169:
------------------------------------

Thank you for the excellent work you have been doing for replication
documentation Kim.

>I can see that implementing the SYSCS_UTIL.SYSCS_PREPARE_REPLICATION procedure would 
>require only a new file in the Reference Manual and some changes to the "Starting and

>running replication" topic of the Admin Guide. 

You are correct in your estimation of the work required to document this stored procedure.
This procedure would be involved only during replication startup and its presence in the
Reference manual in the stored procedures section, and, the Admin guide section for starting
and running replication should suffice

>There was also something in the comments to DERBY-3552 about a possible need for 
>documentation concerning jar files, but I don't quite understand this issue yet so I'm
not 
>sure what would be involved.

There are two possibilities

1) Write documentation saying that, if jars need to be installed when replication is running
for
    the database the user will have to manually copy the jar files to the slave.
2) Disable jar file operations during replication, in which case we will have to document
saying that
    users cannot perform jar operations when replication is running.

I am inclined towards 1) because it gives more flexibility to the user, but I was hoping to
get some more
inputs from the community in the coming days on this, which is why I have left it open.

-----------------------------------------------------------------------------------------------------------------

An example for installing a jar file would be like this

ij> CALL SQLJ.install_jar
('myStuff.jar', 'APP.MyStuffJar', 0);

ij> CALL SYSCS_UTIL.SYSCS_SET_DATABASE_PROPERTY
('derby.database.classpath', 'APP.MyStuffJar');

I found this example here http://wiki.apache.org/db-derby/DerbySQLroutines

> Add documentation for replication
> ---------------------------------
>
>                 Key: DERBY-3169
>                 URL: https://issues.apache.org/jira/browse/DERBY-3169
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.4.0.0
>            Reporter: Jørgen Løland
>            Assignee: Kim Haase
>         Attachments: DERBY-3169-2.diff, DERBY-3169-2.stat, DERBY-3169-2.zip, DERBY-3169-3.diff,
DERBY-3169-3.stat, DERBY-3169-3.zip, DERBY-3169-4.diff, DERBY-3169-4.zip, DERBY-3169-5.diff,
DERBY-3169-5.zip, DERBY-3169.diff, DERBY-3169.stat, DERBY-3169.zip
>
>


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message