Re: Change status service issue fetching more than 10k rows

Hi Rapolas. Thank you for the reply. I understand that there's documentation for the query that must also include a LIMIT clause restricting results to at most 10,000 rows, but please note that this doesn't mean that you can fetch all the data in a split second, Could you elaborate more on why

Re: Change status service issue fetching more than 10k rows

Hello, There is a workaround to fetch change_events with LIMIT greater than 1, as mentioned in this doc from Google which states, *The query must also include a LIMIT clause restricting results to at most 10,000 rows. If you'

RE: Change status service issue fetching more than 10k rows

Hi, Thank you for reaching out to our API support team. To better assist you, could you elaborate on the "How can I fetch all the data in that split second?" concern? As for your other question "How do I know if all the data was fetched?" you can also utilize the return_total_results_count set

RE: Change status service issue fetching more than 10k rows

Hi, Thank you for reaching out to our API support team. To better assist you, could you elaborate on the "How can I fetch all the data in that split second?" concern? As for your other question "How can I fetch all the data in that split second?" you can utilize the return_total_results_count