JanusGraph / JanusGraph/janusgraph
Support Long limit internally
Open
Nobody has claimed this yet.
area/core
- Dominant language
- Java
- Stars
- 5.8k
- Forks
- 1.2k
- Avg merge
- 13h 53m
- Merged PRs (30d)
- 6
Description
Currently limit internally is supported as `int`, but Gremlin supports limit as `long`.
For consistency between Gremlin and JanusGraph as well as eliminating issues like #3341 it would be better to have `limit` as `long` in JanusGraph instead of `int`.
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
The issue does not name files, tests, or entry points. Start by locating internal handling of the limit value and its usages, then trace the affected query paths and existing tests. Done means JanusGraph consistently represents limit as a long and the relevant behavior remains covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100