public class AbstractBTreePartition.SliceableIterator extends AbstractUnfilteredRowIterator implements SliceableUnfilteredRowIterator
columns, isReverseOrder, metadata, partitionKey, partitionLevelDeletion, staticRow, stats| Modifier | Constructor and Description |
|---|---|
protected |
SliceableIterator(ColumnFilter selection,
boolean isReversed) |
| Modifier and Type | Method and Description |
|---|---|
protected Unfiltered |
computeNext() |
java.util.Iterator<Unfiltered> |
slice(Slice slice)
Move forward (resp.
|
close, columns, isReverseOrder, metadata, partitionKey, partitionLevelDeletion, staticRow, statsendOfData, hasNext, next, peek, removeclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitisEmpty, partitionLevelDeletion, statscolumns, isReverseOrder, metadata, partitionKey, staticRowcloseprotected SliceableIterator(ColumnFilter selection, boolean isReversed)
protected Unfiltered computeNext()
computeNext in class AbstractIterator<Unfiltered>public java.util.Iterator<Unfiltered> slice(Slice slice)
SliceableUnfilteredRowIteratorslice.
Please note that successive calls to slice are allowed provided the
slice are non overlapping and are passed in clustering (resp. reverse clustering) order.
However, slice is allowed to leave the iterator in an unknown state and there
is no guarantee over what a call to hasNext or next will yield after
a call to slice. In other words, for a given iterator, you should either use
slice or hasNext/next but not both.
slice in interface SliceableUnfilteredRowIteratorCopyright © 2016 The Apache Software Foundation