Closed Bug 775395 Opened 13 years ago Closed 13 years ago

Remove index_above and index_below in sync2.0?

Categories

(Cloud Services Graveyard :: Server: Sync, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rfkelly, Assigned: rfkelly)

References

Details

(Whiteboard: [qa+])

Attachments

(1 file)

Sync2.0 currently lets you filter BSOs based on their sortindex, using index_above and index_below. It's not clear to me how or why these parameters would be used by the client. Are they currently in use? The server currently does not index on the "sortindex" field so they are not terribly efficient as a filter. If we have no plans to use them, I suggest removing them to simplify the API.
historically, these were so that devices with low connectivity could get the most important items first. Give me the top 100 history items. Now the next 100, etc.
(In reply to Toby Elliott [:telliott] from comment #1) > historically, these were so that devices with low connectivity could get the > most important items first. Give me the top 100 history items. Now the next > 100, etc. Surely that would be achieved via order=index&limit=100, not index_above?
It can be. Back then, we cared more about only getting items over a certain threshold. I suspect we can drop it.
(In reply to Richard Newman [:rnewman] from comment #2) > (In reply to Toby Elliott [:telliott] from comment #1) > > historically, these were so that devices with low connectivity could get the > > most important items first. Give me the top 100 history items. Now the next > > 100, etc. > Surely that would be achieved via order=index&limit=100, not index_above? It would be, if add offset back into the API. Marking the dependency on that bug.
Depends on: 735102
Blocks: 776771
Attachment #645563 - Flags: review?(telliott)
Comment on attachment 645563 [details] [diff] [review] patch removing index_above and index_below I am amused by the if statement that magically went away, but the rest looks good.
Attachment #645563 - Flags: review?(telliott) → review+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [qa+]
Is this to be part of some future deployment? Or something I can just verify and close?
This is long-gone. Close away.
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: