public abstract class AbstractFileGraphProvider extends AbstractGraphProvider
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.GraphProvider.Descriptor, GraphProvider.TestListener
Modifier and Type | Field and Description |
---|---|
protected boolean |
graphSONInput |
protected static Random |
RANDOM |
CORE_IMPLEMENTATIONS
Constructor and Description |
---|
AbstractFileGraphProvider() |
Modifier and Type | Method and Description |
---|---|
void |
clear(Graph graph,
org.apache.commons.configuration2.Configuration configuration)
Clears a
Graph of all data and settings. |
protected String |
getInputLocation(Graph g,
LoadGraphWith.GraphData graphData) |
cleanParameters, deleteDirectory, getBaseConfiguration, loadGraphData, makeTestDirectory, newGraphConfiguration, readIntoGraph
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
clear, convertId, convertLabel, getGraphComputer, getImplementations, getStaticFeatures, getTestListener, getWorkingDirectory, newGraphConfiguration, openTestGraph, standardGraphConfiguration, standardTestGraph, traversal, traversal
protected static final Random RANDOM
protected boolean graphSONInput
public void clear(Graph graph, org.apache.commons.configuration2.Configuration configuration) throws Exception
GraphProvider
Graph
of all data and settings. Implementations will have different ways of handling this.
It is typically expected that Graph.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 the Graph
, 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 the Configuration
as 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.Exception
protected String getInputLocation(Graph g, LoadGraphWith.GraphData graphData)
Copyright © 2013–2022 Apache Software Foundation. All rights reserved.