zxs / tungsten-replicator

Automatically exported from code.google.com/p/tungsten-replicator
0 stars 0 forks source link

Row based replication of TIME values is timezone dependant #741

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
mysql> CREATE TABLE `timetest` (   `id` varchar(36) NOT NULL,   `start_date` 
time DEFAULT NULL,   `end_date` time DEFAULT NULL,   PRIMARY KEY (`id`) ) 
ENGINE=InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected (0.03 sec)

mysql> SET BINLOG_FORMAT='ROW';
Query OK, 0 rows affected (0.00 sec)

mysql> insert into timetest values 
('e3aa97e7-8211-4a5b-ad91-829a8210a27e','02:51:46','05:51:46');
Query OK, 1 row affected (0.01 sec)

mysql> select * from timetest;
+--------------------------------------+------------+----------+
| id                                   | start_date | end_date |
+--------------------------------------+------------+----------+
| e3aa97e7-8211-4a5b-ad91-829a8210a27e | 02:51:46   | 05:51:46 |
+--------------------------------------+------------+----------+
1 row in set (0.00 sec)

In THL, on master :
SEQ# = 5 / FRAG# = 0 (last frag)
- TIME = 2013-10-22 01:44:23.0
- EPOCH# = 0
- EVENTID = mysql-bin.000022:0000000000001647;0
- SOURCEID = ubuntu1
- METADATA = [mysql_server_id=1;dbms_type=mysql;service=firstcluster;shard=test]
- TYPE = com.continuent.tungsten.replicator.event.ReplDBMSEvent
- OPTIONS = [foreign_key_checks = 1, unique_checks = 1]
- SQL(0) =
 - ACTION = INSERT
 - SCHEMA = test
 - TABLE = timetest
 - ROW# = 0
  - COL(1: ) = [B@578cbd65
  - COL(2: ) = 02:51:46
  - COL(3: ) = 05:51:46

On slave :
SEQ# = 5 / FRAG# = 0 (last frag)
- TIME = 2013-10-22 11:44:23.0
- EPOCH# = 0
- EVENTID = mysql-bin.000022:0000000000001647;0
- SOURCEID = ubuntu1
- METADATA = [mysql_server_id=1;dbms_type=mysql;service=firstcluster;shard=test]
- TYPE = com.continuent.tungsten.replicator.event.ReplDBMSEvent
- OPTIONS = [foreign_key_checks = 1, unique_checks = 1]
- SQL(0) =
 - ACTION = INSERT
 - SCHEMA = test
 - TABLE = timetest
 - ROW# = 0
  - COL(1: ) = [B@6acd5f8b
  - COL(2: ) = 12:51:46
  - COL(3: ) = 15:51:46

select * from timetest;
+--------------------------------------+------------+----------+
| id                                   | start_date | end_date |
+--------------------------------------+------------+----------+
| e3aa97e7-8211-4a5b-ad91-829a8210a27e | 12:51:46   | 15:51:46 |
+--------------------------------------+------------+----------+
1 row in set (0.00 sec)

After a consistency check :
pendingExceptionMessage: Consistency check failed on table 'test.timetest' id: 
1, offset: -1, limit: -1, method: 'md5' failed

Original issue reported on code.google.com by stephane...@continuent.com on 22 Oct 2013 at 8:59

GoogleCodeExporter commented 9 years ago
We shall look closely into this at the beginning of next release development 
cycle.

Original comment by linas.vi...@continuent.com on 12 Dec 2013 at 3:46

GoogleCodeExporter commented 9 years ago
postponing

Original comment by stephane...@continuent.com on 30 Jan 2014 at 9:21

GoogleCodeExporter commented 9 years ago

Original comment by stephane...@continuent.com on 30 Jan 2014 at 9:41

GoogleCodeExporter commented 9 years ago
All date/time issues are currently scheduled for 3.1.

Original comment by linas.vi...@continuent.com on 10 Sep 2014 at 12:19

GoogleCodeExporter commented 9 years ago

Original comment by linas.vi...@continuent.com on 19 Jan 2015 at 2:18