Description of problem: a query for an event using rest api didn't filter the results accordingly. e.g. using the example found on the technical guide: GET https://{engine_address}/api/events;from=2795?search=type%3D30 HTTP/1.1 Accept: application/xml also tried the old format: https://{engine_address}/api/events?search=type%3D30&from=2795 playing with the value of the from key, it seems that this parameter is ignored. Actual results: I get all the events of type 30, as well as events with id < 2795 Expected results: I should get all the events of type 30 with id > 2795
As far as I can tell this "from" parameter has never been implemented, so we can remove it from the documentation or implement it as an enhancement for 3.6. What do we want to do?
This is a side effect of the following change: http://gerrit.ovirt.org/28135 Now the "from" parameter of search queries is effectively ignored, no piece of code in the engine calls the SearchContainer.getSearchForm() method.
Eli, can you take a look? I think it is a serious issue, as it breaks backwards compatibility for users of the RESTAPI.
(In reply to Juan Hernández from comment #3) > Eli, can you take a look? I think it is a serious issue, as it breaks > backwards compatibility for users of the RESTAPI. Yes, I agree , this is a real regression! We should restore the 'from' support on top of that patch ...
When was this regression introduced? Should this get backported to 3.4.4 ? Should this block 3.4.4 release when it is present in this version?
This regression was introduced in ovirt-engine-3.5.0_beta1, it doesn't affect 3.4.
Verified with rhevm-3.5.0-0.12.beta.el6ev.noarch. the format: https://{engine_address}/api/events;from=415?search=type%3D30 returns the expected result.
oVirt 3.5 has been released and should include the fix for this issue.