com.bigdata.rdf.sparql.ast

Class ComputedMaterializationRequirement

java.lang.Object

com.bigdata.rdf.sparql.ast.ComputedMaterializationRequirement

All Implemented Interfaces:

INeedsMaterialization, Serializable

public class ComputedMaterializationRequirement
extends Object
implements INeedsMaterialization, Serializable

Computed INeedsMaterialization metadata for an IValueExpression.

Version:

$Id: ComputedMaterializationRequirement.java 5179 2011-09-12 20:13:25Z thompsonbry $

Author:

Bryan Thompson

See Also:

Serialized Form

Nested Class Summary

Nested classes/interfaces inherited from interface com.bigdata.rdf.internal.constraints.INeedsMaterialization

INeedsMaterialization.Requirement

Constructor Summary

Constructors

Constructor and Description
ComputedMaterializationRequirement(INeedsMaterialization.Requirement requirement, Set<IVariable<IV>> varsToMaterialize)
ComputedMaterializationRequirement(IValueExpression<?> ve)

Method Summary

Methods

Modifier and Type	Method and Description
boolean	equals(Object o)
INeedsMaterialization.Requirement	getRequirement() Does the bop always need materialized variables, or can it sometimes operate on inline terms without materialization? If sometimes, we'll run it before the materialization pipeline steps in an effort to avoid unnecessary materialization overhead.
Set<IVariable<IV>>	getVarsToMaterialize()
String	toString()

Methods inherited from class java.lang.Object

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

Constructor Detail

ComputedMaterializationRequirement

public ComputedMaterializationRequirement(INeedsMaterialization.Requirement requirement,
                                  Set<IVariable<IV>> varsToMaterialize)

ComputedMaterializationRequirement

public ComputedMaterializationRequirement(IValueExpression<?> ve)

Method Detail

toString

public String toString()

Overrides:

toString in class Object

getRequirement

public INeedsMaterialization.Requirement getRequirement()

Description copied from interface: INeedsMaterialization

Does the bop always need materialized variables, or can it sometimes operate on inline terms without materialization? If sometimes, we'll run it before the materialization pipeline steps in an effort to avoid unnecessary materialization overhead. If it fails to evaluate for a particular solution, then it will be run again after the materialization steps for that solution.

Specified by:

getRequirement in interface INeedsMaterialization

getVarsToMaterialize

public Set<IVariable<IV>> getVarsToMaterialize()

equals

public boolean equals(Object o)

Overrides:

equals in class Object