Honestly, incremental processing would need to be refactored to make use of this information (which wouldn't be that fun), and I'm also not 100% sure how much of the extra structures that were added to make things work in its absence could then be removed...
So, I'm pretty neutral on this one. Ryan "dev" <[email protected]> wrote on 04/15/2016 12:46:13 PM: > From: "Ansari, Shad" <[email protected]> > To: "[email protected]" <[email protected]> > Date: 04/15/2016 12:46 PM > Subject: Re: [ovs-dev] [PATCH 1/1] ovsdb-idl: Retain column values > of deleted rows until change-track is cleared. > Sent by: "dev" <[email protected]> > > > ovsdb-idl: Retain column values of deleted rows until change-track is > > cleared. > > > > When change tracking is enabled, only the row uuid of deleted rows > is available. > > The column values are unparsed and the ovsdb_datum values are > cleared so they > > are not available for inspection. This change leaves the column > values around > > for inspection. The column values are cleared (unparsed) upon clearing the > > change track. > > > > Signed-off-by: Shad Ansari <[email protected]> > > This is a patch that I had sent last month. Wondering if there is > any interest in this now that incremental processing is going live. > _______________________________________________ > dev mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
