Hi everyone!

The Tungsten Replicator 1.0 Alpha release is posted on Gforge.   Please 
download and take it for a spin.  The community website is located at 
http://community.continuent.com/community/tungsten-replicator.  The Alpha 
release supports MySQL statement replication on multiple platforms.  A list of 
bugs and features is included at the end of this message.

We're continuing to develop this project quite actively.  The next phase of 
development will include more architectural features to make replication fully 
pluggable, as well as many new features and lots of testing.

I would like to invite you to download the release and take it for a spin.

Cheers, Robert

--
Robert Hodges, CTO, Continuent, Inc.
Email:  [EMAIL PROTECTED]
Mobile:  +1-510-501-3728  Skype:  hodgesrm

Bug

    * [TREP-52] - Create database DDL causes slave applier exit
    * [TREP-63] - Installation and configuration documentation clean-up required
    * [TREP-65] - Replicator scripts have miscellaneous small problems
    * [TREP-66] - Master does not process goMaster unless you issue goOnline 
first
    * [TREP-68] - DROP SCHEMA IF EXISTS <schema name> fails
    * [TREP-69] - Log entries do not have timestamps
    * [TREP-71] - Taking slave online before master causes java connection error
    * [TREP-76] - MySQL binlog RAND_EVENT is not supported
    * [TREP-80] - If consistency failure is detected, Applier should emit a 
special event.
    * [TREP-81] - Consistency Checking chapter in documentation is out of date.
    * [TREP-84] - Missing replicator.properties entries in sample file prevent 
configuration and lead to replicator crash
    * [TREP-86] - PDF document has invalid formatting and architecture picture 
is missing
    * [TREP-88] - Tungsten Replicator tries to issue CREATE SCHEMA command on 
MySQL 4.1
    * [TREP-89] - Changes to the Tungsten replicator and commons versions break 
wrapper.conf and cause trepsvc to fail
    * [TREP-92] - Replicator does not properly trap and log exceptions that end 
threads

New Feature

    * [TREP-2] - Modify MySQL binlog extractor to add extracted events in 
persistent seqno mapping
    * [TREP-5] - persistent storage for mapping of replication event to DBMS 
eventlog position
    * [TREP-9] - implement event seqno to MySQL binlog position mapping in 
MySQL database
    * [TREP-10] - implement event seqno to MySQL binlog position mapping in 
filesystem
    * [TREP-30] - Add checksums to all replication events to ensure data 
integrity
    * [TREP-31] - Implement replication of one, all, or some databases per node
    * [TREP-32] - Implement basic master failover procedure for a single 
master/slave pair
    * [TREP-53] - Create basic but comprehensive user guide for replicator
    * [TREP-64] - Add Java Service Wrapper for Tungsten Replicator
    * [TREP-82] - Organize start / control / stop commands into simple, 
platform independent scripts

Task

    * [TREP-14] - Implement Transaction Log History to record replication events
    * [TREP-17] - Remove Message Dispatcher code and dependencies from 
replicator
    * [TREP-44] - Establish API between an Oracle Java Module and a C based 
listener
    * [TREP-58] - Convert all SQL that is used to track tungsten meta data into 
an RDBMS generic form.
    * [TREP-59] - Clean up all warning in builds
    * [TREP-60] - Ensure all code headers and scripts have GVP v2 licenses
    * [TREP-61] - Ensure correct license attribution of all subsidiary code
    * [TREP-62] - Move Tungsten Replicator to separate SVN repository and 
GForge project
    * [TREP-85] - Eliminate all Eclipse warnings from replicator code
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to