|
|
Update - TEXT affected also. But with corrupted data. |
|
|
Update - corrupted data appearing when using reload-node/reload-table only. It looks like [B@312cff16 |
|
|
Reproduce - do reload, every row will be corrupted and truncated. Do update of any record(with correct type at source node) - will be OK. Do with mentioned data types on source node - correct hex representation will be "replicated" |
|
|
ivan.konev, I have tried to reproduce this error following your steps and your notes, but I was not able to recreate this error. If this is still an issue you are noticing, could you post your versions of mysql and symmetricds as well as an example of your tables on each node? Thanks, Max |
|
|
Sure, mysql 5.7 with additional show_compatibility_56=1 , encodings character-set-server=utf8mb4 collation-server=utf8mb4_unicode_ci SymmetricDS 3.8.13 Table template CREATE TABLE `xxx_log` ( `dt` DATETIME(3) NOT NULL DEFAULT '', `xxx` CHAR(128) NOT NULL COLLATE 'utf8_bin', `cam` CHAR(128) NOT NULL COLLATE 'utf8_bin', `text` VARCHAR(21400) NULL DEFAULT NULL COLLATE 'utf8_bin', PRIMARY KEY (`dt`, `xxx`, `cam`), INDEX `idx_dt` (`dt`) ) COLLATE='utf8_bin' ENGINE=InnoDB ROW_FORMAT=COMPRESSED ; Text was originally TEXT/MEDIUMTEXT type. |
|
|
Tables on source and destination are equal. No transforms also. |
|
|
Engine JDBC connection string db.url=jdbc:mysql://127.0.0.1/db?useUnicode=true&characterEncoding=utf8 But changing/removing all paramaters does not gives any change. java/jdbc utf8 equal to full utf8mb4 mysql mentioned above. |
|
|
I have tried copying all of your settings as you described and I was not able to reproduce any similar error. Are there any other setting that might be influencing this error? |
|
|
Well, i will try to post you logs after reproducing this. Sure there MUST be UTF data in TEXT fields, not only 1 byte latin characters. |
|
|
100% reproduced. Definitions as above. I've created table for testing - test. CREATE TABLE `test` ( `id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT, `dt` TIMESTAMP NULL DEFAULT NULL, `text` TEXT NULL COLLATE 'utf8mb4_bin', `char` VARCHAR(200) NULL DEFAULT NULL COLLATE 'utf8mb4_bin', PRIMARY KEY (`id`) ) COLLATE='utf8mb4_bin' ENGINE=InnoDB ; linked it with trigger and trigger_router. 1. Inserting some UTF data - OK(pic), replicated correctly(pic) 2. Making reload node or table ./symadmin reload-table test -p ../engines/home-000.properties -n 001 FAIL, TEXT type column - garbled, varchar - OK (pic) |
|
|
Screenshot 2017-04-14 02.44.55.png (9,716 bytes) |
|
|
Screenshot 2017-04-14 02.45.40.png (76,275 bytes) |
|
|
Screenshot 2017-04-14 02.46.40.png (71,680 bytes) |
|
|
Screenshot 2017-04-14 02.49.37.png (72,720 bytes) |
|
|
Retrying with debug logs. Logs attached. Probably - TEXT recognized as binary. |
|
|
|
- Anonymous