Commit Graph

1619 Commits

Author SHA1 Message Date
Jiri Pechanec
4d76243227 DBZ-1121 Emit ALTER event for updated tables 2019-02-09 20:03:57 +01:00
Gunnar Morling
6a871e1b65 DBZ-983 Expanding test 2019-02-07 15:04:43 +01:00
Jiri Pechanec
eff78cae5a DBZ-983 Handle rounding of defaults 2019-02-07 15:04:43 +01:00
Jiri Pechanec
3487cf1bfb DBZ-983 BigDecimal default value scales according to column 2019-02-07 15:04:43 +01:00
Jiri Pechanec
6637f68861 DBZ-1123 Integration test for generated defaults 2019-02-07 14:06:49 +01:00
Jiri Pechanec
f65cbb7b7d DBZ-1123 Support generated colums 2019-02-07 14:06:49 +01:00
Jiri Pechanec
85ce630ee4 DBZ-1131 Correct log position comparison 2019-02-07 13:55:48 +01:00
Ivan Lorenz
721e8112cd DBZ-1126 Localize era display value to default locale 2019-02-06 15:34:30 +01:00
Jiri Pechanec
d20d3402c9 [release] Changelog for 0.9.0.Final 2019-02-05 08:23:13 +01:00
Gunnar Morling
9fc336dc6d DBZ-1096 Removing unused parameter 2019-02-04 14:49:38 +01:00
Gunnar Morling
10c1214291 DBZ-1118 Adding Kevin Pullin to COPYRIGHT.txt 2019-02-04 14:43:19 +01:00
Gunnar Morling
7076deba5a DBZ-1118 Adding JUnit rule to skip tests depending on Postgres version 2019-02-04 14:43:19 +01:00
Kevin Pullin
c414a8b942 Add test for DBZ-1118 2019-02-04 14:43:19 +01:00
Kevin Pullin
1330df8908 Postgres snapshot - On null records, clear prior value from currentRecord 2019-02-04 14:43:19 +01:00
Jiri Pechanec
16620f0bf9 DBZ-1040 Cleaning up event formatting 2019-02-04 12:39:07 +01:00
Gunnar Morling
99caad60d8 DBZ-1040 Changing resolution of "lag behind source" to milli-seconds;
Also using Duration/Instant types internally.
2019-02-04 12:39:07 +01:00
Gunnar Morling
f1c4234248 DBZ-1040 Removing value from metrics events 2019-02-04 12:39:07 +01:00
Gunnar Morling
913e0bc5c8 DBZ-1040 Making metadata provider a member of Metrics instead of passing it for each onEvent() call 2019-02-04 12:39:07 +01:00
Gunnar Morling
399f91ce84 DBZ-1040 Typo fix 2019-02-04 12:39:07 +01:00
Gunnar Morling
27274d664f DBZ-1040 Passing source as DataCollectionId instead of Object 2019-02-04 12:39:07 +01:00
Jiri Pechanec
de171917dc DBZ-1040 Improve event to string formatting 2019-02-04 12:39:07 +01:00
Jiri Pechanec
a621e43d8b DBZ-1040 Expose transaction id 2019-02-04 12:39:07 +01:00
Jiri Pechanec
213d4a42ca DBZ-1040 Metrics for internal queue 2019-02-04 12:39:07 +01:00
Jiri Pechanec
d993ee265e DBZ-1040 Metrics for lag behind source, offset and tx count 2019-02-04 12:39:07 +01:00
Jiri Pechanec
809cea0ae0 DBZ-1097 High-level design description of SQL Server streaming 2019-02-04 07:19:27 +01:00
Grzegorz Kołakowski
85732f5ccb DBZ-1115 Specify schema name as well while taking schema locks 2019-02-01 06:27:33 +01:00
Gunnar Morling
e9c2f5ee99 DBZ-1116 Log message about missing LSN at WARN level 2019-02-01 06:24:49 +01:00
jchipmunk
acbc94e8b0 DBZ-1112 rename prepareQuery() to prepareQueryWithBlockingConsumer()
Reason:
reference to prepareQuery is ambiguous
[ERROR] both method prepareQuery(java.lang.String,io.debezium.jdbc.JdbcConnection.StatementPreparer,io.debezium.jdbc.JdbcConnection.BlockingResultSetConsumer) in io.debezium.jdbc.JdbcConnection and method prepareQuery(java.lang.String,io.debezium.jdbc.JdbcConnection.StatementPreparer,io.debezium.jdbc.JdbcConnection.ResultSetConsumer) in io.debezium.jdbc.JdbcConnection match
2019-01-30 09:36:09 +01:00
jchipmunk
ff4e38cc46 DBZ-1112 Strings.join() doesn't apply conversation for first element
Replace:
- Integer.parseInt() to Integer.valueOf()
- Short.parseShort() and new Short() to Short.valueOf()
- Long.parseLong() to Long.valueOf()
2019-01-30 09:36:09 +01:00
Gunnar Morling
41b7fbe78e Adding note on testing Postgres connector with external DB 2019-01-30 09:25:12 +01:00
Gunnar Morling
dd01d26d16 DBZ-1113 Pulling up test to MySqlDdlParserTest;
* Adding Joy Gao to COPYRIGHT.txt
* Typo fix
2019-01-30 09:22:05 +01:00
Joy Gao
030cf9ac14 DBZ-1113 allow adding multiple partitions in a single statement 2019-01-30 09:22:05 +01:00
Gunnar Morling
cc0df61665 DBZ-1111 Allowing to use drop-slot-on-close with PG 10 or newer 2019-01-29 14:44:10 +01:00
Gunnar Morling
2a80931d03 DBZ-962 Avoiding Short constructor 2019-01-29 10:28:48 +01:00
Gunnar Morling
e84c6e2238 DBZ-962 Avoiding dependency to JAXB 2019-01-29 10:28:48 +01:00
Jiri Pechanec
d7da674fd7 [release] Missed schema change name from migration notes 2019-01-28 18:04:38 +01:00
Jiri Pechanec
e8f7c616c3 [jenkins-jobs] SQL Server promoted to main repo 2019-01-28 14:59:23 +01:00
Jenkins user
c5b7d21d3e [maven-release-plugin] prepare for next development iteration 2019-01-28 11:07:04 +00:00
Jenkins user
f1ae79ff73 [maven-release-plugin] prepare release v0.9.0.CR1 2019-01-28 11:07:04 +00:00
Jiri Pechanec
1c7c317157 [release] Changelog for 0.9.0.CR1 2019-01-28 11:38:47 +01:00
Jiri Pechanec
32f9543979 DBZ-1103 Make pause before interrupt configurable 2019-01-28 11:07:34 +01:00
Gunnar Morling
ccff79e07d DBZ-1105 Removing TableImpl#columnNames field 2019-01-28 10:23:56 +01:00
Gunnar Morling
2dc80b3cc4 DBZ-947 Adding Grzegorz Kołakowski to COPYRIGHT.txt 2019-01-28 09:32:57 +01:00
Gunnar Morling
a27c29765a DBZ-947 Formatting 2019-01-28 09:32:57 +01:00
Grzegorz Kołakowski
64c45c7490 DBZ-947 Reset initial transaction isolation level at snapshot end 2019-01-28 09:32:57 +01:00
Grzegorz Kołakowski
aa8fb2b478 DBZ-947 Log when schema locks are released 2019-01-28 09:32:57 +01:00
Grzegorz Kołakowski
c5578c055b DBZ-947 Revert default isolation level after initial load 2019-01-28 09:32:57 +01:00
Grzegorz Kołakowski
430d828e86 DBZ-947 Add read_uncommitted snapshot.isolation.mode
During this mode neither table nor row-level locks are taken.
Therefore, other transactions are not affected at all.
However, this mode does not guarantee snapshot consistency.
2019-01-28 09:32:57 +01:00
Grzegorz Kołakowski
0835a8efba DBZ-947 Rename snapshot.locking.mode to snapshot.isolation.mode 2019-01-28 09:32:57 +01:00
Grzegorz Kołakowski
b132f2b704 DBZ-947 Fix semantics of snapshot locking modes
Exclusive mode: this mode takes exclusive locks on all monitored tables
during initial load (as documented).

None mode has been renamed to repeatable read since this name better
reflects its characteristics. None suggests that no locks are acquired.
No table locks are acquired indeed, however, repeatable read takes
shared row locks until the end of the transaction, which effectively
prevents other transactions from updating tables.
Table locks are hold only during schema snapshot.
2019-01-28 09:32:57 +01:00