View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003180 | SymmetricDS | Bug | public | 2017-07-03 16:08 | 2017-07-07 18:13 |
| Reporter | chenson | Assigned To | chenson | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.8.26 | ||||
| Target Version | 3.8.27 | Fixed in Version | 3.8.27 | ||
| Summary | 0003180: When a node is re-registered it can propagate deletes of itself back to the registration effectively unregistering itself | ||||
| Description | Scenario: client group pushes/pulls the server group child group pushes/pulls the server group client group pushes/pulls the child group If you re-open registration of either the child or the client groups deletes of sym_node and sym_node_security are captured at the child or the client group and propagate to the other which in turn propagates to the server. There is no need to ever propagate deletes of "yourself". | ||||
| Tags | No tags attached. | ||||
|
SymmetricDS: 3.8 e5148e22 2017-07-03 14:23:43 Details Diff |
0003180: When a node is re-registered it can propagate deletes of itself back to the registration effectively unregistering itself |
Affected Issues 0003180 |
|
| mod - symmetric-core/src/main/java/org/jumpmind/symmetric/route/ConfigurationChangedDataRouter.java | Diff File | ||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-07-03 16:08 | chenson | New Issue | |
| 2017-07-03 16:08 | chenson | Status | new => assigned |
| 2017-07-03 16:08 | chenson | Assigned To | => chenson |
| 2017-07-03 16:17 | chenson | Project | SymmetricDS Pro => SymmetricDS |
| 2017-07-03 16:32 | chenson | Status | assigned => resolved |
| 2017-07-03 16:32 | chenson | Fixed in Version | => 3.8.27 |
| 2017-07-03 16:32 | chenson | Resolution | open => fixed |
| 2017-07-03 19:00 | chenson42 | Changeset attached | => SymmetricDS 3.8 e5148e22 |
| 2017-07-07 18:13 | chenson | Status | resolved => closed |