[
https://issues.apache.org/jira/browse/BEAM-9873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281212#comment-17281212
]
Beam JIRA Bot commented on BEAM-9873:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> Removing Invalid JSON messages from PCollection before starting BigQueryIO
> Operations
> -------------------------------------------------------------------------------------
>
> Key: BEAM-9873
> URL: https://issues.apache.org/jira/browse/BEAM-9873
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Reporter: Varun
> Priority: P2
> Labels: Clarified, features, stale-P2
>
> In a typical set up of Pub Sub and Cloud Dataflow, a pub sub subscriber might
> receive some messages that does not follow a valid json structure and the Big
> Query Insert operation fails to process these messages and the worker may
> gets terminated if the exception is not handled correctly.
> The likelihood of receiving the invalid json messages are very less and the
> upstream component pushing messages on the Topic should have a validation at
> their end but this is not always the case and the application should be
> robust enough to survive even if there are wrong messages being pushed by the
> Upstreams.
> I have created an Enum which acts like a Predicate in Filter transform. This
> is very standard logic of validating Json and i would like to add this to the
> java SDK(and Python) in the Filter transform
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
