This query doesn't return correct results: /api/events;from=<event_id>;?search=type%3D<type_num> and this one does: /api/events?search=type%3D<type_num>&from=<event_id> from/ should be treated as REST matrix parameter and not ovirt-engine search parameter
What's wrong with the format we currently have? The ";" style parameters have never caught up (and they are supposed to be apply to a path segment only by the way).
the decision to use matrix parameters was made due to: 1. we wanted to create clear differentiation between query (search) parameters and parameters exposed in api only, i.e if user seeing 'max', 'case_sensitive', etc. parameters in api, he will not expect to find them in UI search. 2. Matrix parameters apply to a particular path element while query parameters apply to the request as a whole, so it will give us much more flexibility in the future. 3. matrix parameters can have more than one value, i.e: /matrix_param=value1,value2
I think it's confusing to have two types of parameters. And i don't think #1-#3 above are enough justification for breaking compatibility. But in any case, we cannot break compatibility before 4.0.
(In reply to comment #3) > I think it's confusing to have two types of parameters. wouldn't be more confusing to have only one type of params, while a part of them not available in UI?, and people would confusing when concatenating them to search string doing "... name=X... and case_sensitive = false" while correct format would be: "... name=X..."&&case_sensitive = false as it not really search query param. anyway, non query params documented in /api resource & RSDL & UG > And i don't think > #1-#3 above are enough justification for breaking compatibility. > > But in any case, we cannot break compatibility before 4.0. old style will be kept till 4.0
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: A new syntax for searching for events using the REST API is now supported. The event search URI is now of the form <literal>/api/events;from=</literal><replaceable><event_id></replaceable>. The existing search syntax remains supported but is considered deprecated and will be removed in Red Hat Enterprise Virtualization 4.0.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -A new syntax for searching for events using the REST API is now supported. The event search URI is now of the form <literal>/api/events;from=</literal><replaceable><event_id></replaceable>. The existing search syntax remains supported but is considered deprecated and will be removed in Red Hat Enterprise Virtualization 4.0.+A new syntax for searching for events using the REST API is now supported. The event search URI is now of the form <literal>/api/events;from=</literal><replaceable><event_id></replaceable>. The existing search syntax remains supported but is considered deprecated and will be removed in a future release.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -A new syntax for searching for events using the REST API is now supported. The event search URI is now of the form <literal>/api/events;from=</literal><replaceable><event_id></replaceable>. The existing search syntax remains supported but is considered deprecated and will be removed in a future release.+A new syntax for performing event search using the REST API is now supported. The event search URI is now of the form <literal>/api/events;from=</literal><replaceable><event_id></replaceable>. The existing search syntax remains supported but is considered deprecated and will be removed in a future release.