JanusGraph / JanusGraph/janusgraph
bug dropping graph via ConfiguredGraphFactory
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
when drop a graph via ConfiguredGraphFactory it calls
```
public static void drop(String graphName) throws BackendException, ConfigurationManagementGraphNotEnabledException, Exception {
final StandardJanusGraph graph = (StandardJanusGraph) ConfiguredGraphFactory.close(graphName);
JanusGraphFactory.drop(graph);
removeConfiguration(graphName);
}
```
`JanusGraphFactory.drop(graph);`
has already drop the entire database, then drop the configures via
`configManagementGraph.removeConfiguration(graphName);`
all shall be ok.
but it calls
` removeConfiguration(graphName);`
it reopens the graph, leaving an empty table(using hbase as backend)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ConfiguredGraphFactory.drop(String graphName), then follow the calls to close, JanusGraphFactory.drop, and removeConfiguration. Reproduce the drop against the HBase backend and verify that removing the configuration does not reopen the graph or leave an empty table.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100