JanusGraph / JanusGraph/janusgraph
Add TraversalStrategies based on JanusGraph instance configuration.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
As discussed here: https://github.com/JanusGraph/janusgraph/pull/2189#discussion_r551610977
We should refactor `StandardJanusGraph` to add `TraversalStrategies` depending on specific JanusGraph instance configuration.
If so, we can move `AdjacentVertexHasUniquePropertyOptimizerStrategy.java` into instance creation lifecycle instead of query lifecycle.
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 the linked discussion and inspect StandardJanusGraph together with AdjacentVertexHasUniquePropertyOptimizerStrategy.java. Determine how instance configuration should select TraversalStrategies, then verify that the optimizer is attached during instance creation rather than query processing and that existing behavior remains covered by the project's tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100