<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 18, 2017, at 10:16 AM, Pierre Tardy <<a href="mailto:tardyp@gmail.com" class="">tardyp@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">So we may want to allow administrator to enforce maximal limits in the REST API service.</div><div style="font-family: Helvetica; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">This means that if people want more, they deal with paging in their scripts. gitlab has a default policy of 100 for all their queries.</div><br class="Apple-interchange-newline"></div></blockquote></div><div class=""><br class=""></div>Yes, I think you’ve hit on something….<div class=""><br class=""><div class="">I think the bigger issue is not the maximum upper bound, but a (much smaller) normal upper bound. I think we may be talking about two limits. The absolute one to which you’re referring above is in my mind of lesser importance. There should be a default limit for query results set in the code; overridable via configuration for a particular instance, and further overridable via a query parameter. The default should not be “all” — this simply invites trouble to appear at some point in time, and further I think it’s safe to say that most use cases are not interested in “all”, so this doesn’t even represent a compromise. The few use cases that need lots of data can explicitly set a higher query limit. (The max upper bound, by the way, should be set in code and also overridable in configuration, but not via a query parameter.)</div><div class=""><br class=""></div><div class=""><br class=""></div></div></body></html>