The kernel's WHERE/LIMIT sentence precedes the projection lever on a path where no operator can edit the SQL

Open
  • Is something wrong?
#2,217 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
backend

Research direction

Start with src/core/query/sql.js:95, then compare the projection scan sites in hypaware-core/plugins-workspace/context-graph/src/project.js:90 with the operator-query behavior documented in src/core/commands/query.js:235-237. The issue identifies a test pair as the acceptance check: projection-path refusals omit or replace the kernel’s filter/LIMIT advice, while operator-query refusals retain it. The body labels this review preference and backlog-only, so confirm it has been explicitly delegated before starting.

Written by the indexing model from the issue text.

Description

Source: #2199 at 54a0f1b96340fde3dabc1fd3f0af9581a20ff7e8
Location: src/core/query/sql.js:95, rendered ahead of hypaware-core/plugins-workspace/context-graph/src/project.js:90
Severity: nit

Evidence

A projection refusal reads 'add a WHERE/date filter, a LIMIT, or aggregate instead of selecting raw rows' about SQL the projection owns (project.js scan sites); the operator cannot act on it, the same situation src/core/commands/query.js:235-237 documents for hyp query overview.

Why deferral is safe

The sentence is unhelpful there but not false, and the correct actionable lever follows in the same message, so no reader is left at a dead end. Suppressing kernel prose per-caller needs kernel plumbing (a message-parts or suppress-filter-advice seam) that this change deliberately avoids under the smallest-change rule. Distinct from finding 8 (whose named lever is itself unreachable on one surface) and from round-1 finding 2 (no lever named at all, already fixed); no shared fix is claimed.

Acceptance condition

A caller-budgeted refusal on the projection path omits or replaces the kernel's filter/LIMIT advice while the operator-query path retains it, pinned by a test pair that fails if the advice reappears on the projection path or disappears from the operator path.

Review preference; backlog only. A human may explicitly delegate it with neutral:fix.

Dominant language
JavaScript
Stars
11
Forks
0
Avg merge
2h 49m
Merged PRs (30d)
302

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from hyparam/hypaware

All issues in hyparam/hypaware

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.