-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Bug]: Possible data loss in BigtableIO r/w if timestamp not set (default to epoch) #27022
Comments
This is not related to Beam, it's DataflowTemplate test utility resource manager has wrong setting The cause was found there: GoogleCloudPlatform/DataflowTemplates#759 (comment)
===========
For the job resulting in table missing, use |
Turns out that this could also affect real usage case when Timestamp field is not set, reopen it and keep it as P1 also |
Posible solutions:
|
CC: @mutianf @ahmedabu98 (this also affects xlang Bigtable) |
per #28624 (comment) at least we should add some validation in write transform |
Would the followup be P2 or still P1? |
This is due to user bug (incorrect/epoch) timestamp attached to the cell. The issue is kept open because there is follow up (add warning) can be done so kept P2, and update issue title |
What happened?
Reported from GoogleCloudPlatform/DataflowTemplates#759
When implementing a load test for BigTableIO, we encountered the following:
Dataflow write pipeline logs say that 10M records were written.
However, the read job shows only 1.6M records read.
Using the cbt utility, the cbt -instance count
command found out that BigTableIO write did not work correctly. Despite the fact that the logs say that all 10M records were written, in fact, there were exactly as many in the table as the read pipeline processed (1.6M). Some of the records processed by the write pipeline did not get into the table.2023-06-05_03_51_23-9051905355392445711
2023-06-05_03_58_18-7016807525741705033
project: apache-beam-testing
Issue Priority
Priority: 1 (data loss / total loss of function)
Issue Components
The text was updated successfully, but these errors were encountered: