Limit clause inconsistency

[s3u]

Try

select * from finditems where keywords = 'ipad 2' limit 3

on ql.io/console. This works as expected as the table created as

create table finditems
 on select get from 'http://svcs.ebay.com/services/search/FindingService/v1?OPERATION-NAME=findItemsByKeywords&SERVICE-VERSION=1.8.0&GLOBAL-ID={globalid}&SECURITY-APPNAME={apikey}&RESPONSE-DATA-FORMAT={format}&REST-PAYLOAD&keywords={^keywords}&paginationInput.entriesPerPage={limit}&paginationInput.pageNumber={pageNumber}&outputSelector%280%29=SellerInfo&sortOrder={sortOrder}'
   with aliases format = 'RESPONSE-DATA-FORMAT', json = 'JSON', xml = 'XML'
   using defaults format = 'XML', globalid = 'EBAY-US', sortorder ='BestMatch',
   apikey =  "{config.eBay.apikey}", limit = 10, pageNumber = 1
   resultset 'findItemsByKeywordsResponse.searchResult.item';

Here limit is mapped to a token {limit}.

If the token is not mapped, the limit clause has no effect. This is confusing.

[hochang]

In fact, the param that does page limitation has various names across different apis. It requires human understanding to map limit to the corresponding param

[jasxie]

Let's discuss