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
{{ message }}
This repository was archived by the owner on Mar 26, 2026. It is now read-only.
In the current implementation of createReadStream in table.ts, the end user is supposed to stop the streaming synchronously by calling readStream.end(). If they instead call it asynchronously, setTimeout(() => { readStream.end(); }, 0);, a few records (16 to be precise, that's the default value of highWaterMark for object streams) will still be received.
See the skipped test should be able to stop reading from the read stream when reading asynchronously:
In the current implementation of
createReadStreamintable.ts, the end user is supposed to stop the streaming synchronously by callingreadStream.end(). If they instead call it asynchronously,setTimeout(() => { readStream.end(); }, 0);, a few records (16 to be precise, that's the default value ofhighWaterMarkfor object streams) will still be received.See the skipped test
should be able to stop reading from the read stream when reading asynchronously:nodejs-bigtable/test/readrows.ts
Line 226 in 5c7c5ae