Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

CounterStructuredName

import type { CounterStructuredName } from "https://googleapis.deno.dev/v1/dataflow:v1b3.ts";

Identifies a counter within a per-job namespace. Counters whose structured names are the same get merged into a single value for the job.

interface CounterStructuredName {
componentStepName?: string;
executionStepName?: string;
inputIndex?: number;
name?: string;
origin?: "SYSTEM" | "USER";
originalRequestingStepName?: string;
originalStepName?: string;
originNamespace?: string;
portion?: "ALL" | "KEY" | "VALUE";
workerId?: string;
}

§Properties

§
componentStepName?: string
[src]

Name of the optimized step being executed by the workers.

§
executionStepName?: string
[src]

Name of the stage. An execution step contains multiple component steps.

§
inputIndex?: number
[src]

Index of an input collection that's being read from/written to as a side input. The index identifies a step's side inputs starting by 1 (e.g. the first side input has input_index 1, the third has input_index 3). Side inputs are identified by a pair of (original_step_name, input_index). This field helps uniquely identify them.

§
name?: string
[src]

Counter name. Not necessarily globally-unique, but unique within the context of the other fields. Required.

§
origin?: "SYSTEM" | "USER"
[src]

One of the standard Origins defined above.

§
originalRequestingStepName?: string
[src]

The step name requesting an operation, such as GBK. I.e. the ParDo causing a read/write from shuffle to occur, or a read from side inputs.

§
originalStepName?: string
[src]

System generated name of the original step in the user's graph, before optimization.

§
originNamespace?: string
[src]

A string containing a more specific namespace of the counter's origin.

§
portion?: "ALL" | "KEY" | "VALUE"
[src]

Portion of this counter, either key or value.

§
workerId?: string
[src]

ID of a particular worker.