Issue 2851: _more_changes flag doesn't work properly
Status:  New
Owner: ----
Reported by buczkows...@gmail.com, Aug 21, 2014
************************************************************
***** NOTE: THIS BUG TRACKER IS FOR GERRIT CODE REVIEW *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, INTERNAL *****
***** ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.    *****
***** THOSE ISSUE BELONG IN DIFFERENT ISSUE TRACKERS!  *****
************************************************************

Affected Version: 2.9.0 (in 2.8.0 it worked properly)

What steps will reproduce the problem?
1. Retrieve the newest merged change _sortkey: 
<GERRIT_URL>/a/changes/?q=status:merged&n=1
2. Find _sortkey field and use it below
3. Now I want to get the newest merged changes via API. I call this: <GERRIT_URL>/a/changes/?q=status:merged&n=100&P=<lastSortkey> - where lastSortKey is the sort key of the newest change retrieved in point 2.

What is the expected output? What do you see instead?
First record in result shouldn't have 
"_more_changes": true
if there is no more newer changes.
But I still get this flag set to TRUE, which is wrong in my opinion.

Please provide any additional information below.

Sep 10, 2014
Project Member #1 edwin.ke...@gmail.com
In 2.9 the sortkey was replaced with the S operator [1].

[1] https://gerrit-review.googlesource.com/54509