You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug: nearest() projection passes lint but fails at execution #640
A query projecting the same nearest() expression used for ordering passes lint and then fails with unsupported projection expression: Nearest. This is a compiler/executor contract mismatch, independent of the broader choice of public score API.
Freshly reproduced on released 0.10.0 using local files, a supplied three-dimensional vector and no embedding provider.
Compiler and executor agree: either support a precisely defined score/distance projection, or reject this unsupported projection during compilation with an actionable diagnostic. Do not accept it as executable and fail only after opening/running the query.
Code and regression scope
Compiler type checking and projection execution need a shared capability contract. Test literal-vector and parameterized input, aliasing, null vectors and stored-query compilation. If scores are exposed, verify score meaning/direction rather than only successful serialization.
Related: #606 discusses the broader search/score contract. This issue is the concrete accepted-query/runtime-refusal bug.
Version / environment
Omnigraph 0.10.0; local filesystem; macOS arm64. No @embed, external model, network provider or ANN index is required for this reproduction.
Activity