352d616173
Using current batch size for comparison is wrong in case that when currentScn is topScn as described in DBZ-6155. In the other case (when topScn is behind currentScn) can eventually lead to this situation. when topScn would fall behind currentScn more and more as we would compare currentScn - topScn with bigger and bigger number (current batch size). Comapring with logMiningBatchSizeMin could result in very small window which would mean we will send many small queries instead of several bigger ones during mining. Therefore reverting back to do the adjustments based on the defaultBatchSize. |
||
|---|---|---|
| .. | ||
| cassandra.adoc | ||
| db2.adoc | ||
| index.adoc | ||
| mongodb.adoc | ||
| mysql.adoc | ||
| oracle.adoc | ||
| postgresql.adoc | ||
| spanner.adoc | ||
| sqlserver.adoc | ||
| vitess.adoc | ||