Vasily Ulianko
8e342bea84
DBZ-1689 Allow setting boolean as default value for INT
2020-01-02 11:55:22 +01:00
Gunnar Morling
2c50429ce6
Adding Vedit Firat Arig to COPYRIGHT.txt
2020-01-02 11:51:09 +01:00
Vedit Firat Arig
1bf09c9946
Fixed Doc for checking mysql binlog status
2020-01-02 11:50:15 +01:00
Chris Cranford
4f646a860d
Fix minor formatting of SQL table layout.
2019-12-20 13:06:48 -05:00
Fintan Bolton
e09375861f
DOC-mysql Added toc::[] macro to assembly files
2019-12-20 13:06:48 -05:00
Fintan Bolton
b16f4e7776
DOC-mysql Removed manually created mini-tocs (based on xref links)
2019-12-20 13:06:48 -05:00
Fintan Bolton
945ef31ef5
DOC-mysql Updated navigation text for consistency
2019-12-20 13:06:48 -05:00
Fintan Bolton
6774e32cb6
DOC-mysql Added missing [source,json] formatting in Delete change event value section
2019-12-20 13:06:48 -05:00
Fintan Bolton
47542ba315
DOC-mysql Renamed mysql-intro.adoc to mysql.adoc (as it was previously)
2019-12-20 13:06:48 -05:00
Fintan Bolton
7fc1153085
DOC-mysql Added context attribute to mysql-intro.adoc file
2019-12-20 13:06:48 -05:00
Fintan Bolton
f45215ef69
DOC-fix-xrefs Fix broken links
2019-12-20 13:06:48 -05:00
Fintan Bolton
ebfbd83a90
DOC-removed-modules-attr Stop using the {modules} attribute in doc assembly files
2019-12-20 13:06:48 -05:00
Fintan Bolton
d78c5b7eed
DOC-remote-attribute-includes Removed unnecessary attribute include statements from assembly files
2019-12-20 13:06:48 -05:00
Alex Mansell
ebc846c9a5
Initial modularization of MySQL connector documentation
2019-12-20 13:05:41 -05:00
Debezium Builder
9723c93db9
[maven-release-plugin] prepare for next development iteration
2019-12-18 01:44:33 -05:00
Debezium Builder
09049516f2
[maven-release-plugin] prepare release v1.0.0.Final
2019-12-18 01:44:33 -05:00
Jiri Pechanec
c0dd096e13
[release] Changelog for 1.0.0.Final
2019-12-18 07:36:06 +01:00
Chris Cranford
5c6f8fdd70
DBZ-1680 Fix enum value resolution across all PostgreSQL decoders
2019-12-17 18:21:17 +01:00
Gunnar Morling
66feaa0f22
DBZ-1643 Formatting fix
2019-12-17 18:19:30 +01:00
Gunnar Morling
8408fc6065
DBZ-1643 Adding Johan Venant to COPYRIGHT.txt
2019-12-17 14:07:34 +01:00
Gunnar Morling
91a4d83c4d
DBZ-1643 Another go at fixing non-UTC timestamps
2019-12-17 14:07:34 +01:00
Jiri Pechanec
a80892f628
DBZ-1643 Test timestamp TZ
2019-12-17 09:04:08 +01:00
Gunnar Morling
7c079ca5e5
DBZ-1643 Documentation update
2019-12-17 08:59:55 +01:00
Gunnar Morling
eb4b1dad45
DBZ-1643 Normalizing TZ value to UTC
...
This avoids the need for the database.server.timezone option when running on SQL Server 2016 or newer.
2019-12-17 08:59:55 +01:00
Jiri Pechanec
d886a56596
DBZ-1643 Autoformat the code
2019-12-17 08:59:55 +01:00
Johan Venant
c8070d19b8
DBZ-1643 Manage sql server timestamp timezone
2019-12-17 08:59:55 +01:00
Jiri Pechanec
272413ecd0
DBZ-1676 Upgrade to Kafka 2.4.0
2019-12-17 07:29:30 +01:00
Gunnar Morling
f5b563ff87
DBZ-1671 Propagating exception instead of message only
2019-12-17 07:25:51 +01:00
John Martin
a3129fd596
DBZ-1671 update mysql_connector snapshot locking documentation
2019-12-17 07:23:29 +01:00
John Martin
fc24de8dde
DBZ-1671 add innodb_lock_wait_timeout and update info log
2019-12-17 07:23:29 +01:00
John Martin
3f006f8c0e
DBZ-1671 Adding configurable lock_wait_timeout for mysql connector SnapshotReader
2019-12-17 07:23:29 +01:00
Chris Cranford
debcb95fa2
DBZ-1677 Include root cause when PostgreSQL schema refresh fails during streaming
2019-12-17 07:19:02 +01:00
Jiri Pechanec
761e7440cc
DBZ-1670 Rename Serdes to DebeziumSerdes
2019-12-16 15:05:43 +01:00
Jiri Pechanec
b338660283
DBZ-824 Skip validation for keyless tombstone
2019-12-16 14:31:15 +01:00
Jiri Pechanec
1de53607dc
DBZ-824 Fix tests with invalid field names
2019-12-16 14:31:15 +01:00
Jiri Pechanec
6205f1d6ea
DBZ-824 Assert serialization of every processed record
2019-12-16 14:31:15 +01:00
Jiri Pechanec
52a2946aa5
DBZ-1642 Documentation update
2019-12-16 12:21:19 +01:00
Jiri Pechanec
71ca62a692
DBZ-1642 Added test for changing TX
2019-12-16 06:17:21 +01:00
Jiri Pechanec
c5a4106f3f
DBZ-1642 Snapshot isolation for snapshot; test added
2019-12-13 13:00:39 +01:00
Jiri Pechanec
c6449c956b
DBZ-1642 Added Always On docs
2019-12-13 12:01:48 +01:00
Jiri Pechanec
ea56b636fe
DBZ-1642 Commit tx only for read-only connections
2019-12-13 10:36:02 +01:00
Cobolbaby
f199988609
DBZ-1642 commit() method in JdbcConnection compatible with non autocommit
2019-12-13 10:34:52 +01:00
Cobolbaby
641e24b483
DBZ-1642 Create method called commit() in JdbcConnection class
2019-12-13 10:34:52 +01:00
cobolbaby
8306864c00
DBZ-1642 Support SQL Server Alwayson node
...
Ref: https://issues.redhat.com/browse/DBZ-1642
2019-12-13 10:34:52 +01:00
jcechace
65af38fe5d
DBZ-1658 Allowing MySQL and PostgreSQL to run for downstream
2019-12-12 17:40:54 +01:00
Gunnar Morling
d40641b3ab
DBZ-1666 Formatting
2019-12-12 16:39:10 +01:00
Gunnar Morling
77252304db
Nav fix [no ci]
2019-12-12 16:25:17 +01:00
Gunnar Morling
4e0d1c8c07
DBZ-1667 Adding Nikhil Benesch to COPYRIGHT.txt
2019-12-12 12:54:22 +01:00
Nikhil Benesch
afd69fc7fc
DBZ-1667 Regression test for MySQL dates in snapshot being off by one
...
In Debezium 0.9, if the timezone of the JVM running Debezium had an
earlier offset than the timezone of the MySQL server, any values of type
DATE read by the snapshot reader would be incorrectly shifted backwards
by one day. This was the result of a known bug/deficiency in MySQL's
JDBC connector [0].
This bug was inadvertently fixed in Debezium 0.10 by #913 , which
bypassed the JDBC date retrieval logic to support zero dates, thus also
avoiding the inappropriate timezone shifting logic. However, since the
fix was inadvertent, there was no test to protect against regression.
This commit adds such a regression test. Since the MySQL server used in
tests uses timezone GMT-11, we just need to run a SnapshotReader in
timezone GMT-12 and verify that the dates are computed correctly. This
test fails if added to Debezium 0.9, but passes now thanks to #913 .
Humorously, it is likely someone would have noticed this bug long ago
had the test MySQL server used any other timezone; for example, if the
MySQL server used EST as its timezone, anyone running the tests from the
International Date Line to Chicago would have seen the failure. Bt with
GMT-11 there is only one timezone with a smaller offset, GMT-12, which
is only used by tiny outlying islands of the US.
[0]: https://bugs.mysql.com/bug.php?id=91112
2019-12-12 12:53:44 +01:00
Gunnar Morling
4619f5eb9d
DBZ-1666 Wording fix
2019-12-12 11:56:05 +01:00