Merck / Merck/Halyard

Improve HalyardTupleExprEvaluation.evaluateDescribeOperator

Open
#9 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.evaluateDescribeOperator is pumping data from DescribeIteration
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

Start with HalyardTupleExprEvaluation.evaluateDescribeOperator and trace how it currently pumps data from DescribeIteration. Determine the scope of a pure push evaluation strategy and confirm that the completed work no longer relies on the current data-pumping approach.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.