Merck / Merck/Halyard

Improve HalyardTupleExprEvaluation.evaluateZeroLengthPath

Open
#11 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
114
Forks
18
PR merge metrics
No merged PRs in 30d

Description

HalyardTupleExprEvaluation.evaluateZeroLengthPath is pumping data from ZeroLengthPathIteration
it should be re-implemented to use pure push evaluation strategy

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate HalyardTupleExprEvaluation.evaluateZeroLengthPath and inspect how it currently uses ZeroLengthPathIteration. Trace the surrounding tuple-expression evaluation flow to understand the existing push strategy. Done means the method is re-implemented using pure push evaluation rather than pumping data from ZeroLengthPathIteration.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.