Class FileBasedSink.WriteOperation<DestinationT,OutputT>
- Type Parameters:
OutputT
- the type of values written to the sink.
- All Implemented Interfaces:
Serializable
- Enclosing class:
FileBasedSink<UserT,
DestinationT, OutputT>
FileBasedSink
.
The primary responsibilities of the WriteOperation is the management of output files. During
a write, FileBasedSink.Writer
s write bundles to temporary file locations. After the bundles have been
written,
finalizeDestination(DestinationT, org.apache.beam.sdk.transforms.windowing.BoundedWindow, java.lang.Integer, java.util.Collection<org.apache.beam.sdk.io.FileBasedSink.FileResult<DestinationT>>)
is given a list of the temporary files containing the output bundles.- During finalize, these temporary files are copied to final output locations and named according to a file naming template.
- Finally, any temporary files that were created during the write are removed.
Subclass implementations of WriteOperation must implement createWriter()
to return a concrete FileBasedSinkWriter.
Temporary and Output File Naming:
During the write, bundles are written to temporary files using the tempDirectory that can be
provided via the constructor of WriteOperation. These temporary files will be named
{tempDirectory}/{bundleId}
, where bundleId is the unique id of the bundle. For example, if
tempDirectory is "gs://my-bucket/my_temp_output", the output for a bundle with bundle id 15723
will be "gs://my-bucket/my_temp_output/15723".
Final output files are written to the location specified by the FileBasedSink.FilenamePolicy
. If
no filename policy is specified, then the DefaultFilenamePolicy
will be used. The
directory that the files are written to is determined by the FileBasedSink.FilenamePolicy
instance.
Note that in the case of permanent failure of a bundle's write, no clean up of temporary files will occur.
If there are no elements in the PCollection being written, no output will be generated.
- See Also:
-
Field Summary
FieldsModifier and TypeFieldDescriptionprotected final FileBasedSink
<?, DestinationT, OutputT> The Sink that this WriteOperation will write to.protected boolean
Whether windowed writes are being used. -
Constructor Summary
ConstructorsConstructorDescriptionWriteOperation
(FileBasedSink<?, DestinationT, OutputT> sink) Constructs a WriteOperation using the default strategy for generating a temporary directory from the base output filename.WriteOperation
(FileBasedSink<?, DestinationT, OutputT> sink, ResourceId tempDirectory) Create a new WriteOperation. -
Method Summary
Modifier and TypeMethodDescriptionprotected static ResourceId
buildTemporaryFilename
(ResourceId tempDirectory, String filename) Constructs a temporary file resource given the temporary directory and a filename.abstract FileBasedSink.Writer
<DestinationT, OutputT> Clients must implement to return a subclass ofFileBasedSink.Writer
.protected final List
<KV<FileBasedSink.FileResult<DestinationT>, ResourceId>> finalizeDestination
(@Nullable DestinationT dest, @Nullable BoundedWindow window, @Nullable Integer numShards, Collection<FileBasedSink.FileResult<DestinationT>> existingResults) getSink()
Returns the FileBasedSink for this write operation.void
removeTemporaryFiles
(Collection<ResourceId> filenames) void
Indicates that the operation will be performing windowed writes.toString()
-
Field Details
-
sink
The Sink that this WriteOperation will write to. -
windowedWrites
protected boolean windowedWritesWhether windowed writes are being used.
-
-
Constructor Details
-
WriteOperation
Constructs a WriteOperation using the default strategy for generating a temporary directory from the base output filename.Without windowing, the default is a uniquely named subdirectory of the provided tempDirectory, e.g. if tempDirectory is /path/to/foo/, the temporary directory will be /path/to/foo/.temp-beam-$uuid.
With windowing, the default is a consistent named subdirectory of the provided tempDirectory, e.g. if tempDirectory is /path/to/foo/, the temporary directory will be /path/to/foo/.temp-beam. With windowing, unique subdirectories of the tempDirectory are not beneficial as they cannot be used for cleanup. By using a consistent directory, the created temp files are well-distributed beneath a common directory prefix, across both worker and pipeline executions. This is beneficial for filesystems such as GCS which can reuse autoscaling of the file metadata.
- Parameters:
sink
- the FileBasedSink that will be used to configure this write operation.
-
WriteOperation
Create a new WriteOperation.- Parameters:
sink
- the FileBasedSink that will be used to configure this write operation.tempDirectory
- the base directory to be used for temporary output files.
-
-
Method Details
-
buildTemporaryFilename
protected static ResourceId buildTemporaryFilename(ResourceId tempDirectory, String filename) throws IOException Constructs a temporary file resource given the temporary directory and a filename.- Throws:
IOException
-
getTempDirectory
-
createWriter
Clients must implement to return a subclass ofFileBasedSink.Writer
. This method must not mutate the state of the object.- Throws:
Exception
-
setWindowedWrites
public void setWindowedWrites()Indicates that the operation will be performing windowed writes. -
removeTemporaryFiles
- Throws:
IOException
-
finalizeDestination
protected final List<KV<FileBasedSink.FileResult<DestinationT>,ResourceId>> finalizeDestination(@Nullable DestinationT dest, @Nullable BoundedWindow window, @Nullable Integer numShards, Collection<FileBasedSink.FileResult<DestinationT>> existingResults) throws Exception - Throws:
Exception
-
getSink
Returns the FileBasedSink for this write operation. -
toString
-