As part of our sharded database optimization efforts, we made changes to add an implicit timestamp range to some APIs to limit how many shards they can scan in one query. This means customers could potentially get no results and no next link but still have results.
Solution
As a performance compromise we can populate the next link for these type of requests if we clamped the timestamp range and there's less than limit results.
Problem
As part of our sharded database optimization efforts, we made changes to add an implicit timestamp range to some APIs to limit how many shards they can scan in one query. This means customers could potentially get no results and no next link but still have results.
Solution
As a performance compromise we can populate the next link for these type of requests if we clamped the timestamp range and there's less than
limitresults.Alternatives
No response