Class MapElements<InputT,OutputT>
- All Implemented Interfaces:
Serializable,HasDisplayData
PTransforms for mapping a simple function over the elements of a PCollection.- See Also:
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic classAPTransformthat adds exception handling toMapElements. -
Field Summary
Fields inherited from class org.apache.beam.sdk.transforms.PTransform
annotations, displayData, name, resourceHints -
Method Summary
Modifier and TypeMethodDescription<NewFailureT>
MapElements.MapWithFailures<InputT, OutputT, NewFailureT> exceptionsInto(TypeDescriptor<NewFailureT> failureTypeDescriptor) Returns a newMapElements.MapWithFailurestransform that catches exceptions raised while mapping elements, with the given type descriptor used for the failure collection but the exception handler yet to be specified usingMapElements.MapWithFailures.exceptionsVia(ProcessFunction).<FailureT> MapElements.MapWithFailures<InputT, OutputT, FailureT> exceptionsVia(InferableFunction<WithFailures.ExceptionElement<InputT>, FailureT> exceptionHandler) Returns a newMapElements.MapWithFailurestransform that catches exceptions raised while mapping elements, passing the raised exception instance and the input element being processed through the givenexceptionHandlerand emitting the result to a failure collection.expand(PCollection<? extends InputT> input) Override this method to specify how thisPTransformshould be expanded on the givenInputT.static <OutputT> MapElements<?, OutputT> into(TypeDescriptor<OutputT> outputType) Returns a newMapElementstransform with the given type descriptor for the output type, but the mapping function yet to be specified usingvia(ProcessFunction).voidpopulateDisplayData(DisplayData.Builder builder) Register display data for the given transform or component.<NewInputT>
MapElements<NewInputT, OutputT> via(Contextful<Contextful.Fn<NewInputT, OutputT>> fn) Likevia(ProcessFunction), but supports access to context, such as side inputs.static <InputT,OutputT>
MapElements<InputT, OutputT> via(InferableFunction<InputT, OutputT> fn) ForInferableFunction<InputT, OutputT>fn, returns aPTransformthat takes an inputPCollection<InputT>and returns aPCollection<OutputT>containingfn.apply(v)for every elementvin the input.<NewInputT>
MapElements<NewInputT, OutputT> via(ProcessFunction<NewInputT, OutputT> fn) For aProcessFunction<InputT, OutputT>fnand output type descriptor, returns aPTransformthat takes an inputPCollection<InputT>and returns aPCollection<OutputT>containingfn.apply(v)for every elementvin the input.<NewInputT>
MapElements<NewInputT, OutputT> via(SerializableFunction<NewInputT, OutputT> fn) Binary compatibility adapter forvia(ProcessFunction).static <InputT,OutputT>
MapElements<InputT, OutputT> via(SimpleFunction<InputT, OutputT> fn) Binary compatibility adapter forvia(InferableFunction).Methods inherited from class org.apache.beam.sdk.transforms.PTransform
addAnnotation, compose, compose, getAdditionalInputs, getAnnotations, getDefaultOutputCoder, getDefaultOutputCoder, getDefaultOutputCoder, getKindString, getName, getResourceHints, setDisplayData, setResourceHints, toString, validate, validate
-
Method Details
-
via
public static <InputT,OutputT> MapElements<InputT,OutputT> via(InferableFunction<InputT, OutputT> fn) ForInferableFunction<InputT, OutputT>fn, returns aPTransformthat takes an inputPCollection<InputT>and returns aPCollection<OutputT>containingfn.apply(v)for every elementvin the input.InferableFunctionhas the advantage of providing type descriptor information, but it is generally more convenient to specify output type viainto(TypeDescriptor), and provide the mapping as a lambda expression tovia(ProcessFunction).Example usage:
PCollection<String> words = ...; PCollection<Integer> wordsPerLine = words.apply(MapElements.via( new InferableFunction<String, Integer>() { public Integer apply(String word) throws Exception { return word.length(); } })); -
via
Binary compatibility adapter forvia(InferableFunction). -
into
Returns a newMapElementstransform with the given type descriptor for the output type, but the mapping function yet to be specified usingvia(ProcessFunction). -
via
For aProcessFunction<InputT, OutputT>fnand output type descriptor, returns aPTransformthat takes an inputPCollection<InputT>and returns aPCollection<OutputT>containingfn.apply(v)for every elementvin the input.Example usage:
PCollection<Integer> wordLengths = words.apply( MapElements.into(TypeDescriptors.integers()) .via((String word) -> word.length())); -
via
Binary compatibility adapter forvia(ProcessFunction). -
via
public <NewInputT> MapElements<NewInputT,OutputT> via(Contextful<Contextful.Fn<NewInputT, OutputT>> fn) Likevia(ProcessFunction), but supports access to context, such as side inputs. -
expand
Description copied from class:PTransformOverride this method to specify how thisPTransformshould be expanded on the givenInputT.NOTE: This method should not be called directly. Instead apply the
PTransformshould be applied to theInputTusing theapplymethod.Composite transforms, which are defined in terms of other transforms, should return the output of one of the composed transforms. Non-composite transforms, which do not apply any transforms internally, should return a new unbound output and register evaluators (via backend-specific registration methods).
- Specified by:
expandin classPTransform<PCollection<? extends InputT>,PCollection<OutputT>>
-
populateDisplayData
Description copied from class:PTransformRegister display data for the given transform or component.populateDisplayData(DisplayData.Builder)is invoked by Pipeline runners to collect display data viaDisplayData.from(HasDisplayData). Implementations may callsuper.populateDisplayData(builder)in order to register display data in the current namespace, but should otherwise usesubcomponent.populateDisplayData(builder)to use the namespace of the subcomponent.By default, does not register any display data. Implementors may override this method to provide their own display data.
- Specified by:
populateDisplayDatain interfaceHasDisplayData- Overrides:
populateDisplayDatain classPTransform<PCollection<? extends InputT>,PCollection<OutputT>> - Parameters:
builder- The builder to populate with display data.- See Also:
-
exceptionsInto
public <NewFailureT> MapElements.MapWithFailures<InputT,OutputT, exceptionsIntoNewFailureT> (TypeDescriptor<NewFailureT> failureTypeDescriptor) Returns a newMapElements.MapWithFailurestransform that catches exceptions raised while mapping elements, with the given type descriptor used for the failure collection but the exception handler yet to be specified usingMapElements.MapWithFailures.exceptionsVia(ProcessFunction).See
WithFailuresdocumentation for usage patterns of the returnedWithFailures.Result. -
exceptionsVia
public <FailureT> MapElements.MapWithFailures<InputT,OutputT, exceptionsViaFailureT> (InferableFunction<WithFailures.ExceptionElement<InputT>, FailureT> exceptionHandler) Returns a newMapElements.MapWithFailurestransform that catches exceptions raised while mapping elements, passing the raised exception instance and the input element being processed through the givenexceptionHandlerand emitting the result to a failure collection.This method takes advantage of the type information provided by
InferableFunction, meaning that a call toexceptionsInto(TypeDescriptor)may not be necessary.See
WithFailuresdocumentation for usage patterns of the returnedWithFailures.Result.Example usage:
Result<PCollection<String>, String>> result = words.apply( MapElements .into(TypeDescriptors.integers()) .via((String word) -> 1 / word.length) // Could throw ArithmeticException .exceptionsVia(new WithFailures.ExceptionAsMapHandler<String>() {})); PCollection<Integer> output = result.output(); PCollection<String> failures = result.failures();
-