View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003941 | SymmetricDS | Improvement | public | 2019-05-08 16:04 | 2022-08-02 14:46 |
| Reporter | pmarzullo | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.10.3 | ||||
| Target Version | 3.14.0 | Fixed in Version | 3.14.0 | ||
| Summary | 0003941: Data gap route reader could use multiple queries when exceeding max gaps | ||||
| Description | Currently the routing algorithm uses a configuration parameter (routing.max.gaps.to.qualify.in.sql, defaults to 100) to determine if the routing algorithm will query for unrouted data ids that are in the sym_data_gap records using a database query (if the number of data gaps is less than the configured value) or in memory (get a list of data ids and check in the sym_data_gap records in memory). Instead of switching to the in memory mode of checking, maybe consider that the algorithm will always use the SQL query, but use multiple queries to cover all of the sym_data_gaps records, breaking up the list of sym_data_gap records into manageable numbers per query. | ||||
| Tags | routing | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-05-08 16:04 | pmarzullo | New Issue | |
| 2019-05-08 16:04 | pmarzullo | Tag Attached: routing | |
| 2019-05-08 17:14 | admin | Summary | Change algorithm for routing when using data gaps to always use data gaps => Data gap route reader could use multiple queries when exceeding max gaps |
| 2022-08-02 14:46 | elong | Relationship added | related to 0005210 |
| 2022-08-02 14:46 | elong | Assigned To | => elong |
| 2022-08-02 14:46 | elong | Status | new => closed |
| 2022-08-02 14:46 | elong | Resolution | open => fixed |
| 2022-08-02 14:46 | elong | Fixed in Version | => 3.14.0 |