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] Updated: (DERBY-3205) Replication: Add connection url command options for starting, stopping slave and for failover
Date Wed, 30 Jan 2008 10:02:17 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

V.Narayanan updated DERBY-3205:
-------------------------------

    Attachment: failover_impl_3205_v2.stat
                failover_impl_3205_v2.diff

Thank you for the review and comments on the patch Jorgen!

I have fixed issues 1-6 pointed out and have raised Derby-3364 for 7.

>4) There are two Attribute.java files. I'm not sure if both are in use, but previously

>replication attributes have been added to both files. We either need some insight on 
>which file can be ignored or continue to add the attributes to both files.

I used the following comments to in  org.apache.derby.iapi.reference.Attributes to
conclude that we need to place the failover attribute in both the files.

    "At some point this class should be replaced by
    org.apache.derby.shared.common.reference.Attribute.
    The issue is that this class is used by ij to check attributes,
    ij uses reflection on this class to get the list of valid attributes.
    The expanded class in shared has the client attributes as well.
    Ideally ij would work of an explicit list of attributes and not
    infer the set from reflection. See DERBY-1151"

I shall run tests on this patch and shall post results by today evening.

> Replication: Add connection url command options for starting, stopping slave and for
failover
> ---------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3205
>                 URL: https://issues.apache.org/jira/browse/DERBY-3205
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>    Affects Versions: 10.4.0.0
>            Reporter: Jørgen Løland
>            Assignee: V.Narayanan
>         Attachments: derby-3205_startslave_dontcommit.diff, derby-3205_startslave_dontcommit.stat,
failover_impl_3205_NotForCommit_v1.diff, failover_impl_3205_NotForCommit_v1.stat, failover_impl_3205_v1.diff,
failover_impl_3205_v1.stat, failover_impl_3205_v2.diff, failover_impl_3205_v2.stat, Socket_Close_Fix_v1.diff,
Socket_Close_Fix_v1.stat, startSlave_1a.diff, startSlave_1a.stat, startSlave_1b.diff, startSlave_1b.stat,
startSlave_1c.diff, startSlave_1d.diff, StopSlave_impl_3205_NotForCommit_v1.diff, StopSlave_impl_3205_NotForCommit_v1.stat,
stopSlave_v1a.diff, stopSlave_v1a.stat, stopSlave_v1b.diff, stopSlave_v1b.stat
>
>
> Add commands to start and stop the replication slave using properties or connection url.
Example:
> 'jdbc:derby:<host><dbname>;startSlave=true';
> 'jdbc:derby:<host><dbname>;stopSlave=true';
> 'jdbc:derby:<host><dbname>;failover=true;
> Connection url options that must be recognized:
> startSlave=true
> stopSlave=true
> failover=true
> slaveHost=<host> (optional, defaults to localhost) (only for startSlave)
> slavePort=<port> (optional, defaults to 8001) (only for startSlave)
> See functional specification on Derby-2872 for further details.

-- 
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