[
https://issues.apache.org/jira/browse/BEAM-13376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17488377#comment-17488377
]
Ning commented on BEAM-13376:
-----------------------------
[~kenn] This should be a variation of BEAM-13606.
The root cause is not in Beam. The Bigtable client swallows some errors. I've
also filed a ticket on Github to them:
https://github.com/googleapis/python-bigtable/issues/485.
> Missing error for nonexistent column family BigTable
> ----------------------------------------------------
>
> Key: BEAM-13376
> URL: https://issues.apache.org/jira/browse/BEAM-13376
> Project: Beam
> Issue Type: Bug
> Components: io-java-gcp
> Reporter: PierreOberholzer
> Priority: P1
>
> Currently, there is no error thrown by BigTable in case the Column Families
> are not defined at writing time. That is a misleading behavior as the user
> believes the job has completed, though with empty table.
> A bug was raised on BigTable:
> [https://issuetracker.google.com/issues/186053077?pli=1]
> But it should be made sure that the Beam IO will log this error appropriately.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
