public class IncrementalIndexRowHolder extends Object implements LongColumnSelector
get()/set(org.apache.druid.segment.incremental.IncrementalIndexRow) holder of IncrementalIndexRow. It is used
to implement various machinery around IncrementalIndex, e. g. IncrementalIndexColumnSelectorFactory, IncrementalIndexRowIterator, etc.
By implementing LongColumnSelector, IncrementalIndexRowHolder plays the role of timestamp column selector, to
avoid unneeded level of indirection when timestamp column is selected in IncrementalIndexColumnSelectorFactory.makeColumnValueSelector(String).EMPTY_ARRAY| Constructor and Description |
|---|
IncrementalIndexRowHolder() |
| Modifier and Type | Method and Description |
|---|---|
IncrementalIndexRow |
get() |
long |
getLong() |
void |
inspectRuntimeShape(RuntimeShapeInspector inspector)
Implementations of this method should call
inspector.visit() with all fields of this class, which meet two
conditions:
1. |
boolean |
isNull()
Returns true if the primitive long, double, or float value returned by this selector should be treated as null.
|
void |
set(IncrementalIndexRow currEntry) |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitclassOfObject, getDouble, getFloat, getObjectpublic IncrementalIndexRow get()
public void set(IncrementalIndexRow currEntry)
public long getLong()
getLong in interface BaseLongColumnValueSelectorpublic boolean isNull()
BaseNullableColumnValueSelectorBaseLongColumnValueSelector.getLong(), BaseDoubleColumnValueSelector.getDouble()
and BaseFloatColumnValueSelector.getFloat() must check this method first, or else they may improperly
use placeholder values returned by the primitive get methods.
Users of BaseObjectColumnValueSelector.getObject() should not call this method. Instead, call "getObject"
and check if it is null.isNull in interface BaseNullableColumnValueSelectorpublic void inspectRuntimeShape(RuntimeShapeInspector inspector)
HotLoopCalleeinspector.visit() with all fields of this class, which meet two
conditions:
1. They are used in methods of this class, annotated with CalledFromHotLoop
2. They are either:
a. Nullable objects
b. Instances of HotLoopCallee
c. Objects, which don't always have a specific class in runtime. For example, a field of type Set could be HashSet or TreeSet in runtime, depending on how
this instance (the instance on which inspectRuntimeShape() is called) is configured.
d. ByteBuffer or similar objects, where byte order matters
e. boolean flags, affecting branch taking
f. Arrays of objects, meeting any of conditions a-e.inspectRuntimeShape in interface HotLoopCalleeCopyright © 2011–2020 The Apache Software Foundation. All rights reserved.