feat: add bgp_jan2024_workload SQL corpus test (200 queries, ASAPQuery PR #561) - #219
Merged
Merged
Conversation
…561) Copies the 200-query bgp_jan2024_rrc00 analyst workload from ASAPQuery PR #561 verbatim as YAML (byte-identical to the source blob, plus a trailing newline added by this repo's end-of-file pre-commit hook) and lowers each query under SqlDialect::ClickhouseSQL against a bgp.bgp_updates catalog widened with the BGP-attribute columns the workload references directly (origin, next_hop, local_pref, med, communities, atomic, aggr_asn, aggr_ip, source_file). Unlike bgp_analytics (15 hand-picked queries, pinned per-query), this corpus pins an aggregate tally by error category rather than an exact per-query outcome: at 200 queries a per-query needle would mean 200 hand-maintained entries, and DataFusion's "Did you mean 'x'?" spelling suggestion is non-deterministic across process runs, so message-snippet needles on Plan errors would be flaky. The category tally is stable and still ratchets regressions. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
milindsrivastava1997
changed the title
This was referenced Aug 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
bgp_jan2024_rrc00analyst workload, lowered underSqlDialect::ClickhouseSQL.bgp.bgp_updatespast the existing 15-querybgp_analyticscorpus's 7-column schema with the 9 extra BGP-attribute columns this workload references directly (origin,next_hop,local_pref,med,communities,atomic,aggr_asn,aggr_ip,source_file), modeled asUtf8since every query wraps the numeric-looking ones intoString/toInt64OrZero/toFloat64OrZeroand treats''as a missing-value sentinel.bgp_analytics.rs(15 hand-picked queries, exact per-query pinning), this corpus pins an aggregate tally by error category rather than a per-query outcome: at 200 queries a per-query message-snippet needle would mean 200 hand-maintained entries, and DataFusion'sPlan-error "Did you mean 'x'?" spelling suggestion is confirmed non-deterministic across process runs, so needling that text would be flaky. The category split (Lowered/Plan/Schema/Parse/NotImplemented/UnsupportedFeature/Other) is stable across repeated runs and still ratchets regressions.Lowered: 64, Plan: 127, NotImplemented: 3, UnsupportedFeature: 6(0 inSchema,Parse,Other).Run using
cargo test -p asap-frontend-sql --test bgp_jan2024_workload -- --nocapture