I found a case. After submit a spark app, we can stop or getState by JavaStreamingContext. But use beam api,we can’t stop or getState for pipeline. I think should add stop and getState method in PipelineRunner.
发件人: James [mailto:[email protected]] 发送时间: 2017年2月22日 9:50 收件人: [email protected] 主题: Is it possible that a feature which the underlying engine (e.g. Spark) supports, but cann't be expressed using Beam API? Is it possible that a feature which the underlying engine (e.g. Spark) supports, but cann't be expressed using Beam API? If there is really such a case, how to handle it? (we are planning to use Beam as the data processing API, but have this concern here.) Thanks in advance.
