JanusGraph / JanusGraph/janusgraph
some strange nodes
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
gremlin> g.V()
02:36:25 WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes
==>v[4192]
==>v[81924288]
==>v[81928384]
gremlin> g.V().valueMap()
02:36:35 WARN org.janusgraph.graphdb.transaction.StandardJanusGraphTx - Query requires iterating over all vertices [()]. For better performance, use indexes
==>[]
java.lang.NullPointerException
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
Reproduce the reported g.V() and g.V().valueMap() queries in a JanusGraph environment and capture the full stack trace for the NullPointerException. Start from StandardJanusGraphTx, which emits the warning, and compare the returned vertices with valueMap() behavior. Done means the failure is isolated and a concrete fix scope and regression test are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100