com.bigdata.bop.rdf.join

Class ChunkedMaterializationIterator

java.lang.Object

com.bigdata.bop.rdf.join.ChunkedMaterializationIterator

All Implemented Interfaces:

ICloseable, ICloseableIterator<IBindingSet[]>, Iterator<IBindingSet[]>

public class ChunkedMaterializationIterator
extends Object
implements ICloseableIterator<IBindingSet[]>

Iterator pattern for chunked materialization.

Version:

$Id$

Author:

Bryan Thompson

See Also:

ChunkedMaterializationOp

Constructor Summary

Constructors

Constructor and Description
ChunkedMaterializationIterator(IVariable<?>[] vars, LexiconRelation lex, boolean materializeInlineIVs, ICloseableIterator<IBindingSet[]> src)

Method Summary

Methods

Modifier and Type	Method and Description
void	close() Closes the iterator, releasing any associated resources.
boolean	hasNext()
IBindingSet[]	next()
void	remove()

Methods inherited from class java.lang.Object

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

Constructor Detail

ChunkedMaterializationIterator

public ChunkedMaterializationIterator(IVariable<?>[] vars,
                              LexiconRelation lex,
                              boolean materializeInlineIVs,
                              ICloseableIterator<IBindingSet[]> src)

Parameters:

vars - The variables to be materialized (required; must not be an empty array).

lex - The LexiconRelation.

materializeInlineIVs - When true, inline IVs will also be materialized.

src - The source iterator.

Method Detail

close

public void close()

Description copied from interface: ICloseableIterator

Closes the iterator, releasing any associated resources. This method MAY be invoked safely if the iterator is already closed. Implementations of this interface MUST invoke 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.

Specified by:

close in interface ICloseable

Specified by:

close in interface ICloseableIterator<IBindingSet[]>

hasNext

public boolean hasNext()

Specified by:

hasNext in interface Iterator<IBindingSet[]>

next

public IBindingSet[] next()

Specified by:

next in interface Iterator<IBindingSet[]>

remove

public void remove()

Specified by:

remove in interface Iterator<IBindingSet[]>