Fix so that operational store correctly removes bridge-other-configs 56/18156/4
authorEd Warnicke <eaw@cisco.com>
Sun, 12 Apr 2015 00:06:02 +0000 (17:06 -0700)
committerEd Warnicke <eaw@cisco.com>
Mon, 13 Apr 2015 17:48:13 +0000 (10:48 -0700)
commit487cdb26c00b4adb276d2f0bb711a9b6b6f68401
tree98d3ad0da7e4b45fb537a2c04310a68f7a02c70c
parent1b903597200f668f7771226863ac48f508c5ddff
Fix so that operational store correctly removes bridge-other-configs

Before, if a bridge-other-configs entry was removed on ovsdb, we didn't
remove it from the operational store.

This is an artifact of using *merge* rather than *put*.
Using merge is *still* a good idea for us, but what was happening
was basically this.

Say we got a report in the operational store of

[bridge-other-configs1, bridge-other-configs2]

which we dutifully merged.

Then we got a report of
[bridge-other-configs2]

when that is *merged*... the protocol1 entry is left dangling,
because its a *merge*.  To compensate, we have to be *very*
specific about wanting to remove bridge-other-configs1.

Change-Id: Ic94b67b341bf7233c881e324f494c6701b622131
Signed-off-by: Ed Warnicke <eaw@cisco.com>
southbound/southbound-impl/src/main/java/org/opendaylight/ovsdb/southbound/transactions/md/OvsdbBridgeUpdateCommand.java