org.apache.druid.segment.loading

Class NoopDataSegmentPusher

java.lang.Object

org.apache.druid.segment.loading.NoopDataSegmentPusher

All Implemented Interfaces:

DataSegmentPusher

public class NoopDataSegmentPusher
extends Object
implements DataSegmentPusher

Mostly used for test purpose.

Field Summary

Fields inherited from interface org.apache.druid.segment.loading.DataSegmentPusher

JOINER

Constructor Summary

Constructors

Constructor and Description
NoopDataSegmentPusher()

Method Summary

Modifier and Type	Method and Description
String	getPathForHadoop()
String	getPathForHadoop(String dataSource) Deprecated.
Map<String,Object>	makeLoadSpec(URI uri)
DataSegment	push(File file, DataSegment segment, boolean replaceExisting) Pushes index files and segment descriptor to deep storage.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface org.apache.druid.segment.loading.DataSegmentPusher

generateUniquePath, getAllowedPropertyPrefixesForHadoop, getDefaultStorageDir, getStorageDir, getStorageDir, makeIndexPathName

Constructor Detail

NoopDataSegmentPusher

public NoopDataSegmentPusher()

Method Detail

getPathForHadoop

public String getPathForHadoop()

Specified by:

getPathForHadoop in interface DataSegmentPusher

getPathForHadoop

@Deprecated
public String getPathForHadoop(String dataSource)

Deprecated.

Specified by:

getPathForHadoop in interface DataSegmentPusher

push

public DataSegment push(File file,
                        DataSegment segment,
                        boolean replaceExisting)

Description copied from interface: DataSegmentPusher

Pushes index files and segment descriptor to deep storage.

Specified by:

push in interface DataSegmentPusher

Parameters:

file - directory containing index files

segment - segment descriptor

replaceExisting - if true, pushes to a unique file path. This prevents situations where task failures or replica tasks can either overwrite or fail to overwrite existing segments leading to the possibility of different versions of the same segment ID containing different data. As an example, a Kafka indexing task starting at offset A and ending at offset B may push a segment to deep storage and then fail before writing the loadSpec to the metadata table, resulting in a replacement task being spawned. This replacement will also start at offset A but will read to offset C and will then push a segment to deep storage and write the loadSpec metadata. Without unique file paths, this can only work correctly if new segments overwrite existing segments. Suppose that at this point the task then fails so that the supervisor retries again from offset A. This 3rd attempt will overwrite the segments in deep storage before failing to write the loadSpec metadata, resulting in inconsistencies in the segment data now in deep storage and copies of the segment already loaded by historicals. If unique paths are used, caller is responsible for cleaning up segments that were pushed but were not written to the metadata table (for example when using replica tasks).

Returns:

segment descriptor

makeLoadSpec

public Map<String,Object> makeLoadSpec(URI uri)

Specified by:

makeLoadSpec in interface DataSegmentPusher