fix: Infer singular quantileXxxMerge() from MV quantilesXxxState()#2154
fix: Infer singular quantileXxxMerge() from MV quantilesXxxState()#2154
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 532258d The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
🔵 Tier 2 — Low RiskSmall, isolated change with no API route or data model modifications. Why this tier:
Review process: AI review + quick human skim (target: 5–15 min). Reviewer validates AI assessment and checks for domain-specific concerns. Stats
|
PR Review✅ No critical issues found. The fix is correct and minimal — One minor observation (not blocking): the existing test suite apparently already covers |
E2E Test Results✅ All tests passed • 146 passed • 3 skipped • 1148s
Tests ran across 4 shards in parallel. |
Summary
This PR fixes a bug in the quantile function inference used for MV queries. For MVs defined with
quantilesXxxState()columns, HyperDX will now infer aquantileXxxMergefunction instead of aquantilesXxxMergefunction.quantilesXxxMergereturns an array result, which is incompatible with HyperDX's chart implementations.I've tested that quantile, quantileTDigest, and quantileExact all return equivalent results when querying
quantileXxxMergeandquantilesXxxMergefrom aquantilesXxxStatecolumn.Screenshots or video
Before:
After:
How to test locally or on Vercel
This can be tested locally by creating a MV as follows and registering it in the Traces source configuration:
References
quantilesState#2153