Repository navigation
BigTableInstance.getRows sometimes returns 0 values silently #1757
Description
Activity
- addedapi: bigtableIssues related to the Bigtable API.Issues related to the Bigtable API.
on Oct 31, 2016 So I believe in v1 you weren't allowed to send more than 1mb worth of keys (after serialization). I'm not sure if such a limit exists in v2 however.
/cc @lesv
@lesv any insight on this one? Thanks!
@callmehiphop anyone else from Bigtable you can ping for us?
I don't know enough about this case to give a clear answer. Is the table populated with data for each of the keys? Has someone tried to reproduce this case? There isn't a known issue for the service failing, but I can to reproduce this with java and see if it succeeds.
@callmehiphop wdyt?
@arbesfeld are you still seeing this?
I'm not sure - I did a workaround by making requests to Bigtable with smaller chunks of keys and that seemed to fix the issue.
Cool, I think we can close this out. We have a note in our docs advising to chunk up requests as well.
- added a commit that references this issue
on Mar 18, 2026 - added a commit that references this issue
on Mar 27, 2026 - added a commit that references this issue
on May 5, 2026
I noticed when running
getRowsthat I would sometimes get 0 results. No error was thrown so this took a while to uncover, and eventually I had to do it in batches:I'm not sure if this is even the right approach, since 1000 seems pretty arbitrary.
Potentially this is related to #1755? However I was only using ~9k keys which where ~100 characters each which should be under the 4mb limit.