> It doesn't make any mention of differences based on final pipeline state. > So I would interpret it to mean counters should also be available for > canceled pipelines.
Good point! Thanks! On 2017-11-13 11:19, Scott Wegner <[email protected]> wrote: > The javadoc for the Metrics utility states [1]: > > "It is runner-dependent whether Metrics are accessible during pipeline > execution or only after jobs have completed." > > It doesn't make any mention of differences based on final pipeline state. > So I would interpret it to mean counters should also be available for > canceled pipelines. > > I'm not familiar with other runners, but the Dataflow runner makes counters > available after a pipeline is canceled. > > [1] https://beam.apache.org/documentation/sdks/javadoc/2.1.0/ > > On Thu, Nov 9, 2017 at 9:25 PM [email protected] <[email protected]> > wrote: > > > Hello, > > > > Does Beam outline what runners should do if a user queries MetricsResult > > after a pipeline has been cancelled? I understand this is an experimental > > feature and is a work in progress, but I could not find this detail in the > > mailing lists, BEAM-147 [1], or the Aggregator->Metrics Doc [2] > > > > Thanks, > > Paul Gerver > > > > [1] https://issues.apache.org/jira/browse/BEAM-147 > > [2] > > https://docs.google.com/document/d/1voyUIQ2DrWkoY-BsJwM8YvF4gGKB76CDG8BYL8XBc7A/edit#heading=h.vv2fbulkp7t > > > -- > > > Got feedback? http://go/swegner-feedback >
