Improve HalyardTupleExprEvaluation.evaluateArbitraryLengthPath
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 114
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
HalyardTupleExprEvaluation.evaluateArbitraryLengthPath is pumping data from PathIteration
it should be re-implemented to use pure push evaluation strategy
Contributor guide
No contributing guide indexed for this repository
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 in HalyardTupleExprEvaluation.evaluateArbitraryLengthPath and trace how it currently uses PathIteration. Review the surrounding evaluation flow before determining how a pure push evaluation strategy should replace it. Done means the method no longer pumps data from PathIteration while preserving arbitrary-length path evaluation behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100