-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
row.exists() promise is never resolved for the emulator #555
Comments
@igorbernstein2 thank you for the bug report. |
I'm still investigating, but it looks like if you explicitly provide a project ID, it behaves as expected: -const table = require('@google-cloud/bigtable')()
+const table = require('@google-cloud/bigtable')({ projectId: '...' }) |
I have tried to test this further with 4 different node version and 2 different bigtable version, however the workaround did not work. The console.log below is never really seen, and the program just exited from there. Note: Using client version Here's the snippet that I used
For more context here is the environment that I used
Steps to reproduce:
|
Try again using the latest version of the emulator and
|
This was fixed in version 3.0.0-beta.0 of nodejs-bigtable. |
Environment details
@google-cloud/bigtable
version: 2.1.0Steps to reproduce
The log line
this is never seen!
is never printed. However if you run this against a prod instance (by unsettingBIGTABLE_EMULATOR_HOST
envvar), the line is printed. The same is true of row.get().It seems like the read rows
end
event is not being properly propagated when connecting to the emulator. I can't figure out what grpc-node is doing differently for the go emulator, but other languages don't seem to have an issue (ie. grpc-java is able to detect end of stream for readRows in the emulator just fine).The text was updated successfully, but these errors were encountered: