Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

New Features of CMT 2013.08


New features of CMT 2013.08

 

1. User defined data handler

In the column mapping view of the object mapping step, users can define a data handler which is responsible for transform the data read from source to the data which will be written into target. And if this data handler is specified, the CMT will not do any transforming work about the column data during the migration.

This setting includes two parts: the jar file name and the full class name of the handler in the jar file.

 

The jar file should be in the "handlers" directory of the migration application’s working directory, for example:

The handler class must implement a method "public Object convert(Map<String,Object> recordMap,String columnName)", for example:

 

package com.cubrid.migration;

public class TestConvert {
    public Object convert(Map<String,Object> recordMap,String columnName) {
        return "Test for data handler:"  + recordMap.get(columnName);
    }
}

 

Parameter "recordMap" stores the record’s column and data information: the key of the map is source table’s column name and the value of the map is the column’s data.

Parameter "columnName" is the current source table’s column name to be handled.

Return value should be the data which will be inserted into target.

 

During the migration, the method "convert" will be called to convert the data from source to the data which will be written into target.

And all dependences of the handler class should be packaged into the jar file to ensure the handler can work well.


2. New table view in the migration history management:

1. The table view can provide more information about the migration histories.

2. The column "Migration name" is the migration script name when the migration started.

3. The column "Status":

a) "Accomplished": there is no error in the migration;

b) "Not Accomplished": there are errors found in the migration;

c) "Canceled": the migration started failed.

4. Context menus are added for the migration history items.

5. "Migration name filter" can help users to find the migration histories by migration name. It supports "*" as a wildcard to take place of any character or any words.

6. The table viewer can re-sort the items by clicking the column "Migration name" and the column "Start time".

 

3. Open target directory

If the migration target is local files, an output directory will be displayed in the migration report.

And the directory will be opened by clicking the text.

 

4. Re-migrate the SQL files filled with the error records’ insert statements

This feature is available only the migration target is an online database.

 

And the option "Write the records which can’t be inserted into target database to files" should be checked in the selection target database page.

With upper options, the records which can’t be inserted into the target database will be written into some SQL files as insert statements.

 

When the migration finished, Clicking "Restart migration" in the migration history management view, if the history recorded some errors, a new dialog will be popped and a new option will be displayed as follows:

 

Check this option and click the "OK", a SQL importing wizard will be opened:

comments powered by Disqus
Page info
viewed 1365 times
translations en
Author
posted 11 months ago by
kevinlin79
Contributors
updated 11 months ago by
View revisions
tagged
Share this article