[ https://issues.apache.org/jira/browse/BEAM-6304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Etienne Chauchot resolved BEAM-6304. ------------------------------------ Fix Version/s: Not applicable Resolution: Won't Fix As it received no update, I guess the user followed my advice and implemented it as a pre-processing DoFn > can ElasticsearchIO add a ExceptionHandlerFn > --------------------------------------------- > > Key: BEAM-6304 > URL: https://issues.apache.org/jira/browse/BEAM-6304 > Project: Beam > Issue Type: New Feature > Components: io-java-elasticsearch > Affects Versions: Not applicable > Reporter: big > Assignee: Etienne Chauchot > Priority: P2 > Labels: stale-assigned > Fix For: Not applicable > > > I use ElasticsearchIO to write my data to elasticSearch. However, the data is > from other platform and not easy to check its validity. If we get the invalid > data, we can ignore it( even though use batch insert, we can ignore all of > them). So, I wish has a registered exception catch function to process it. > From now on, I read the source code about write function in ProcessElement, > it just throw the exception and cause my job to stop. > I can catch pipeline.run().waitUntilFinish() on direct runner and force it > run again use while statement ungracefully. However, when it deploy to Flink, > it will fail because Flink report exception that it cannot optimize the job. > If there is a method let user to decide how to process exception is required. -- This message was sent by Atlassian Jira (v8.3.4#803005)