Issue Summary

The limit and offset values for database queries are automatically included as part of Bitbucket's paging helper code. Currently, there is no way to increase the offset without increasing the page size of the request.

The offset is incremented by the number of results on each page. Therefore, to retrieve more results at once, the page size would need to be increased. This means that the page size must be increased in the base request.

However, the page sizes are hardcoded. We currently support hibernate.jdbc_batch_size, but we do not support hibernate.jdbc_fetch_size at this time, which would allow us to alter the minimum number of rows fetched.

Expected Results

We want to add a specific property to the bitbucket.properties file to customize the offset value. 

Actual Results

There is no way to customize this value at the moment. 

SELECT this_.id AS id1_98_0_, this_.is_archived AS is_archi2_98_0_, this_.store_id AS store_i13_98_0_, this_.description AS descript3_98_0_, this_.is_forkable AS is_forka4_98_0_, this_.hierarchy_id AS hierarch5_98_0_, this_.name AS name6_98_0_, this_.partition_id AS partitio7_98_0_, this_.project_id AS project14_98_0_, this_.is_public AS is_publi8_98_0_, this_.is_read_only AS is_read_9_98_0_, this_.scm_id AS scm_id10_98_0_, this_.slug AS slug11_98_0_, this_.state AS state12_98_0_, this_1_.origin_id AS origin_i1_124_0_ FROM repository this_ LEFT OUTER JOIN sta_repo_origin this_1_ ON this_.id = this_1_.repository_id ORDER BY lower(this_.name) ASC, this_.id ASC LIMIT 2147311546 OFFSET 172100