public static class AvroIO.Write<T> extends PTransform<PCollection<T>,PDone>
AvroIO.write(java.lang.Class<T>)
All methods in this class delegate to the appropriate method of AvroIO.TypedWrite
.
This class exists for backwards compatibility, and will be removed in Beam 3.0.
name, resourceHints
Modifier and Type | Method and Description |
---|---|
PDone |
expand(PCollection<T> input)
Override this method to specify how this
PTransform should be expanded on the given
InputT . |
void |
populateDisplayData(DisplayData.Builder builder)
Register display data for the given transform or component.
|
AvroIO.Write<T> |
to(DynamicAvroDestinations<T,?,T> dynamicDestinations)
Deprecated.
Use
FileIO.write() or FileIO.writeDynamic() instead. |
AvroIO.Write<T> |
to(FileBasedSink.FilenamePolicy filenamePolicy)
See
TypedWrite#to(FilenamePolicy) . |
AvroIO.Write<T> |
to(ResourceId outputPrefix)
|
AvroIO.Write<T> |
to(java.lang.String outputPrefix)
|
AvroIO.Write<T> |
to(ValueProvider<java.lang.String> outputPrefix)
|
AvroIO.Write<T> |
toResource(ValueProvider<ResourceId> outputPrefix)
|
AvroIO.Write<T> |
withCodec(CodecFactory codec)
|
AvroIO.Write<T> |
withDatumWriterFactory(AvroSink.DatumWriterFactory<T> datumWriterFactory)
|
AvroIO.Write<T> |
withMetadata(java.util.Map<java.lang.String,java.lang.Object> metadata)
|
AvroIO.Write<T> |
withNumShards(int numShards)
|
<DestinationT> |
withOutputFilenames()
Specify that output filenames are wanted.
|
AvroIO.Write<T> |
withoutSharding()
|
AvroIO.Write<T> |
withSchema(Schema schema)
|
AvroIO.Write<T> |
withShardNameTemplate(java.lang.String shardTemplate)
|
AvroIO.Write<T> |
withSuffix(java.lang.String filenameSuffix)
|
AvroIO.Write<T> |
withTempDirectory(ResourceId tempDirectory)
|
AvroIO.Write<T> |
withTempDirectory(ValueProvider<ResourceId> tempDirectory)
|
AvroIO.Write<T> |
withWindowedWrites()
|
compose, compose, getAdditionalInputs, getDefaultOutputCoder, getDefaultOutputCoder, getDefaultOutputCoder, getKindString, getName, getResourceHints, setResourceHints, toString, validate
public AvroIO.Write<T> to(java.lang.String outputPrefix)
@Experimental(value=FILESYSTEM) public AvroIO.Write<T> to(ResourceId outputPrefix)
public AvroIO.Write<T> to(ValueProvider<java.lang.String> outputPrefix)
@Experimental(value=FILESYSTEM) public AvroIO.Write<T> toResource(ValueProvider<ResourceId> outputPrefix)
public AvroIO.Write<T> to(FileBasedSink.FilenamePolicy filenamePolicy)
TypedWrite#to(FilenamePolicy)
.@Deprecated public AvroIO.Write<T> to(DynamicAvroDestinations<T,?,T> dynamicDestinations)
FileIO.write()
or FileIO.writeDynamic()
instead.public AvroIO.Write<T> withSchema(Schema schema)
@Experimental(value=FILESYSTEM) public AvroIO.Write<T> withTempDirectory(ValueProvider<ResourceId> tempDirectory)
public AvroIO.Write<T> withTempDirectory(ResourceId tempDirectory)
public AvroIO.Write<T> withShardNameTemplate(java.lang.String shardTemplate)
public AvroIO.Write<T> withSuffix(java.lang.String filenameSuffix)
public AvroIO.Write<T> withNumShards(int numShards)
public AvroIO.Write<T> withoutSharding()
public AvroIO.Write<T> withWindowedWrites()
public AvroIO.Write<T> withCodec(CodecFactory codec)
public AvroIO.Write<T> withDatumWriterFactory(AvroSink.DatumWriterFactory<T> datumWriterFactory)
public <DestinationT> AvroIO.TypedWrite<T,DestinationT,T> withOutputFilenames()
The nested AvroIO.TypedWrite
transform always has access to output filenames, however due
to backwards-compatibility concerns, AvroIO.Write
cannot return them. This method simply
returns the inner AvroIO.TypedWrite
transform which has WriteFilesResult
as its
output type, allowing access to output files.
The supplied DestinationT
type must be: the same as that supplied in to(DynamicAvroDestinations)
if that method was used, or Void
otherwise.
public AvroIO.Write<T> withMetadata(java.util.Map<java.lang.String,java.lang.Object> metadata)
public PDone expand(PCollection<T> input)
PTransform
PTransform
should be expanded on the given
InputT
.
NOTE: This method should not be called directly. Instead apply the PTransform
should
be applied to the InputT
using the apply
method.
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).
expand
in class PTransform<PCollection<T>,PDone>
public void populateDisplayData(DisplayData.Builder builder)
PTransform
populateDisplayData(DisplayData.Builder)
is invoked by Pipeline runners to collect
display data via DisplayData.from(HasDisplayData)
. Implementations may call super.populateDisplayData(builder)
in order to register display data in the current namespace,
but should otherwise use subcomponent.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.
populateDisplayData
in interface HasDisplayData
populateDisplayData
in class PTransform<PCollection<T>,PDone>
builder
- The builder to populate with display data.HasDisplayData