org.openstreetmap.osmosis.core.customdb.v0_5
Class WriteDataset

java.lang.Object
  extended by org.openstreetmap.osmosis.core.customdb.v0_5.WriteDataset
All Implemented Interfaces:
Completable, Releasable, Task, Sink

public class WriteDataset
extends java.lang.Object
implements Sink

Receives input data as a stream and builds a dataset containing all of the data.

Author:
Brett Henderson

Constructor Summary
WriteDataset(java.io.File directory, boolean enableWayTileIndex)
          Creates a new instance.
 
Method Summary
 void complete()
          Ensures that all information is fully persisted.
 void process(EntityContainer entityContainer)
          Process the entity.
 void release()
          Performs resource cleanup tasks such as closing files, or database connections.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

WriteDataset

public WriteDataset(java.io.File directory,
                    boolean enableWayTileIndex)
Creates a new instance.

Parameters:
directory - The directory to store all data files in.
enableWayTileIndex - If true a tile index is created for ways, otherwise a node-way index is used.
Method Detail

process

public void process(EntityContainer entityContainer)
Process the entity.

Specified by:
process in interface Sink
Parameters:
entityContainer - The entity to be processed.

complete

public void complete()
Ensures that all information is fully persisted. This includes database commits, file buffer flushes, etc. Implementations must call complete on any nested Completable objects. Where the releasable method of a Releasable class should be called within a finally block, this method should typically be the final statement within the try block.

Specified by:
complete in interface Completable

release

public void release()
Performs resource cleanup tasks such as closing files, or database connections. This must be called after all processing is complete and may be called multiple times. Implementations must call release on any nested Releasable objects. It should be called within a finally block to ensure it is called in exception scenarios.

Specified by:
release in interface Releasable