public class OwlSameAsPropertiesExpandingIterator extends Object implements IChunkedOrderedIterator<ISPO>
Modifier and Type | Field and Description |
---|---|
protected static org.apache.log4j.Logger |
log |
DEFAULT_CHUNK_SIZE
Constructor and Description |
---|
OwlSameAsPropertiesExpandingIterator(IV s,
IV p,
IV o,
AbstractTripleStore db,
IV sameAs,
IKeyOrder<ISPO> keyOrder) |
Modifier and Type | Method and Description |
---|---|
void |
close()
Closes the iterator, releasing any associated resources.
|
IKeyOrder<ISPO> |
getKeyOrder()
The natural order in which elements are being visited.
|
boolean |
hasNext() |
ISPO |
next()
The next element available from the iterator.
|
ISPO[] |
nextChunk()
Return the next "chunk" from the iterator.
|
ISPO[] |
nextChunk(IKeyOrder<ISPO> keyOrder)
Return the next "chunk" of elements.
|
void |
remove()
Removes the last element visited by
IChunkedIterator.next() (optional operation). |
public IKeyOrder<ISPO> getKeyOrder()
IChunkedOrderedIterator
getKeyOrder
in interface IChunkedOrderedIterator<ISPO>
null
if not known.public ISPO[] nextChunk()
IChunkedIterator
nextChunk
in interface IChunkedIterator<ISPO>
public ISPO[] nextChunk(IKeyOrder<ISPO> keyOrder)
IChunkedOrderedIterator
IChunkedOrderedIterator.getKeyOrder()
would return non-null
and the request order corresponds to the value that would be returned by
IChunkedOrderedIterator.getKeyOrder()
then the elements in the next chunk are NOT
sorted. Otherwise the elements in the next chunk are sorted before they
are returned. The size of the chunk is up to the implementation.nextChunk
in interface IChunkedOrderedIterator<ISPO>
keyOrder
- The natural order for the elements in the chunk.public ISPO next()
IChunkedIterator
public void remove()
IChunkedIterator
IChunkedIterator.next()
(optional operation).
Note: This method is not readily suited for use with IChunkedIterator.nextChunk()
since the latter has already visited everything in the chunk and
IChunkedIterator.remove()
would only remove the last item in the chunk. Normally
you will want to accumulate items to be removed in a buffer and then
submit the buffer to some batch api operation when it overflows.
Alternatively, the IRangeQuery.REMOVEALL
flag may be used with
the source iterator to remove elements from the index as they are
visited.
public void close()
ICloseableIterator
ICloseableIterator.close()
if Iterator.hasNext()
method returns false
to ensure that the iterator is closed
(and its resources release) as soon as it is exhausted.
Note: Implementations that support Iterator.remove()
MUST NOT
eagerly close the iterator when it is exhausted since that would make it
impossible to remove the last visited statement. Instead they MUST wait
for an explicit ICloseableIterator.close()
by the application.
close
in interface ICloseable
close
in interface ICloseableIterator<ISPO>
Copyright © 2006–2019 SYSTAP, LLC DBA Blazegraph. All rights reserved.