Feature Request: Ability to page through more than a maximum of 1000 results

[GoogleCodeExporter]

Name of affected component: Realtime Reporting API

Issue summary:
No paging for the realtime resource 
(https://developers.google.com/analytics/devguides/reporting/realtime/v3/referen
ce/data/realtime#resource).

Steps to reproduce issue:
1. Make a request to the realtime get endpoint 
(https://developers.google.com/analytics/devguides/reporting/realtime/v3/referen
ce/data/realtime/get) which will return more than 1000 results.

Expected output:
Results capped at some maximum number, but with some sort of paging information 
to get all the results in pages.

Actual results:
A maximum of 1000 results and no ability to page further.

Original issue reported on code.google.com by chrisbr...@industrialcodebox.com on 22 Jan 2016 at 11:06

[GoogleCodeExporter]

Hi,
we found the solution for this issue just adding the max-results clause.

Example:
GoogleAnalyticsConnectorV3_RealtimeData:
LOAD dim_rt_pagePath as [PageFullPath] ,
metric_rt_activeUsers as [ActiveUsers] 
FROM      
[http://localhost:5555/QVSource/GoogleAnalyticsConnectorV3/?table=RealtimeData&a
ppID=&realtimeQuery=ids%3dga%3a2210229%26metrics%3drt%3aactiveUsers%26dimensions
%3drt%3apagePath%26max-results%3d2000%26sort%3d-rt%3aactiveUsers] ( qvx);

Best regards,
Walter Olaizola

Original comment by walter.o...@sdggroup.com on 22 Jan 2016 at 11:15

[GoogleCodeExporter]

Walter's example refers to our QVSource product which wrappers the API so might 
not make sense to other users of the API.

However it does point out that the max-results parameter does appear to allow 
this number to be increased above 1000.

But the question still remains what the maximum possible number is for 
max-results and if there is a cap (and perhaps in any case) should support be 
added for paging?

Original comment by chrisbr...@industrialcodebox.com on 22 Jan 2016 at 11:20

[GoogleCodeExporter]

Links back to http://stackoverflow.com/q/34785740/1841839

Original comment by laurl...@gmail.com on 22 Jan 2016 at 11:44