Package org.apache.tinkerpop.gremlin
Class AbstractFileGraphProvider
java.lang.Object
org.apache.tinkerpop.gremlin.AbstractGraphProvider
org.apache.tinkerpop.gremlin.AbstractFileGraphProvider
- All Implemented Interfaces:
GraphProvider
A base
GraphProvider that is typically for use with Hadoop-based graphs as it enables access to the various
resource data files that are used in the tests.- Author:
- Stephen Mallette (http://stephen.genoprime.com)
-
Nested Class Summary
Nested classes/interfaces inherited from interface org.apache.tinkerpop.gremlin.GraphProvider
GraphProvider.Descriptor, GraphProvider.TestListener -
Field Summary
FieldsFields inherited from interface org.apache.tinkerpop.gremlin.GraphProvider
CORE_IMPLEMENTATIONS -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionvoidClears aGraphof all data and settings.protected StringgetInputLocation(Graph g, LoadGraphWith.GraphData graphData) Methods inherited from class org.apache.tinkerpop.gremlin.AbstractGraphProvider
cleanParameters, deleteDirectory, getBaseConfiguration, loadGraphData, makeTestDirectory, newGraphConfiguration, readIntoGraphMethods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitMethods inherited from interface org.apache.tinkerpop.gremlin.GraphProvider
clear, convertId, convertLabel, getGraphComputer, getImplementations, getStaticFeatures, getTestListener, getWorkingDirectory, newGraphConfiguration, openTestGraph, standardGraphConfiguration, standardTestGraph, traversal, traversal
-
Field Details
-
RANDOM
-
graphSONInput
protected boolean graphSONInput
-
-
Constructor Details
-
AbstractFileGraphProvider
public AbstractFileGraphProvider()
-
-
Method Details
-
clear
public void clear(Graph graph, org.apache.commons.configuration2.Configuration configuration) throws Exception Description copied from interface:GraphProviderClears aGraphof all data and settings. Implementations will have different ways of handling this. It is typically expected thatGraph.close()will be called and open transactions will be closed. For a brute force approach, implementers can simply delete data directories provided in the configuration. Implementers may choose a more elegant approach if it exists. Implementations should be able to accept an argument of null for theGraph, in which case the only action that can be performed is a clear given the configuration. The method will typically be called this way as clean up task on setup to ensure that a persisted graph has a clear space to create a test graph. Implementations should be able to accept an argument of null for theConfigurationas well, and a proper handling is needed. Otherwise, a NullPointerException may be thrown. Calls to this method may occur multiple times for a specific test. Develop this method to be idempotent.- Throws:
Exception
-
getInputLocation
-