You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there's a limit of about 100 topics when calling Kane.Topic.all function, as the pubsub API paginates the results. There are several ways of removing this 100 topic limit, but the easiest one is, by default, traversing the next pages.
When listing topics, we get a map of the following kind:
We can GET projects/#{project}/topics?pageToken=#{page_token} to get the next page. If we use this recursively we can get all of the tokens until the map no longer has the nextPageToken present and we conclude that's the last page.
The text was updated successfully, but these errors were encountered:
We can proceed on that idea in that same PR or we can move to a different one, I'm open to discuss ideas! That PR was tested with a pubsub with more than 100 topics and it worked without any issues.
Currently there's a limit of about 100 topics when calling
Kane.Topic.all
function, as the pubsub API paginates the results. There are several ways of removing this 100 topic limit, but the easiest one is, by default, traversing the next pages.When listing topics, we get a map of the following kind:
We can
GET projects/#{project}/topics?pageToken=#{page_token}
to get the next page. If we use this recursively we can get all of the tokens until the map no longer has thenextPageToken
present and we conclude that's the last page.The text was updated successfully, but these errors were encountered: