Igor Bernstein

Sorry for missing this, but bigtable service will reject microseconds that are not a multiple of 1000. So removing these checks from the emulator is counterproductive

Also, consider moving this to bttest/ so that it can be used programmatically

We are working on a fix for in the client library. We have been able to reproduce this issue and are working on fix for this

We've narrowed down the issue to a race condition in a stream Transform: https://github.com/googleapis/nodejs-bigtable/blob/436e77807e87e13f80ac2bc2c43813b09090000f/src/table.ts#L885 The transform (toRowStream) references the state of previous node in the pipeline (chunktransformer) as a signal...

We have a potential fix in this pr: https://github.com/googleapis/nodejs-bigtable/pull/1284/files Would it be possible for you to confirm that it fixes your use case?

Thanks for the quick response. We are having trouble reproducing the issue with the fix applied. Just to double check that we are running the same code. May I ask...

great to hear! We will cut a release, please let us know if you encounter any other issues

Hi, I'm not sure if this is the best path forward. Cloud Bigtable has 2 features that are designed specifically for this usecase. Have you explored [Audit Logs](https://cloud.google.com/bigtable/docs/audit-logging) and [Change...