| Message ID | 20200507112028.31976.20915.stgit@dceara.remote.csb |
|---|---|
| State | Superseded |
| Headers | show |
| Series | Avoid ovsdb-idl IDL inconsistencies. | expand |
On Thu, May 7, 2020 at 4:20 AM Dumitru Ceara <dceara@redhat.com> wrote: > > Monitor_cond_change might trigger updates to be sent to clients as results > to condition changes. These updates can be either update2 (for monitor_cond > monitors) or update3 (for monitor_cond_since monitors). The documentation > used to mention only update2. > > Signed-off-by: Dumitru Ceara <dceara@redhat.com> > --- > Documentation/ref/ovsdb-server.7.rst | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/Documentation/ref/ovsdb-server.7.rst b/Documentation/ref/ovsdb-server.7.rst > index 967761b..0441435 100644 > --- a/Documentation/ref/ovsdb-server.7.rst > +++ b/Documentation/ref/ovsdb-server.7.rst > @@ -316,9 +316,9 @@ monitor request, <table-updates2> will contain any matched rows by old > condition and not matched by the new condition. > > Changes according to the new conditions are automatically sent to the client > -using the ``update2`` monitor notification. An update, if any, as a result of > -a condition change, will be sent to the client before the reply to the > -``monitor_cond_change`` request. > +using the ``update2`` or ``update3`` monitor notification depending on the > +monitor method. An update, if any, as a result of a condition change, will > +be sent to the client before the reply to the ``monitor_cond_change`` request. > > 4.1.14 Update2 notification > --------------------------- > > _______________________________________________ > dev mailing list > dev@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-dev Acked-by: Han Zhou <hzhou@ovn.org>
diff --git a/Documentation/ref/ovsdb-server.7.rst b/Documentation/ref/ovsdb-server.7.rst index 967761b..0441435 100644 --- a/Documentation/ref/ovsdb-server.7.rst +++ b/Documentation/ref/ovsdb-server.7.rst @@ -316,9 +316,9 @@ monitor request, <table-updates2> will contain any matched rows by old condition and not matched by the new condition. Changes according to the new conditions are automatically sent to the client -using the ``update2`` monitor notification. An update, if any, as a result of -a condition change, will be sent to the client before the reply to the -``monitor_cond_change`` request. +using the ``update2`` or ``update3`` monitor notification depending on the +monitor method. An update, if any, as a result of a condition change, will +be sent to the client before the reply to the ``monitor_cond_change`` request. 4.1.14 Update2 notification ---------------------------
Monitor_cond_change might trigger updates to be sent to clients as results to condition changes. These updates can be either update2 (for monitor_cond monitors) or update3 (for monitor_cond_since monitors). The documentation used to mention only update2. Signed-off-by: Dumitru Ceara <dceara@redhat.com> --- Documentation/ref/ovsdb-server.7.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)