feat(querier): rfc0018.4 green — event_name DSL filter

[jensholdgaard]

RFC 0018 green (1/6) — event_name as a first-class DSL filter (RFC0018.4)

Adds event_name to the logs DSL, mirroring the existing scope bare field exactly:

• Field::EventName variant (string-operand) in dsl/ir.rs
• lexed/parsed (dsl/parse.rs), structured-IR mapped (dsl/structured.rs), rendered (dsl/display.rs)
• compiled to the RFC 0005 event_name column (compile.rs: column_of, is_text_field, field_name, string_call_column)

The event_name column already existed (RFC 0005 §3.2) — only the query surface was missing it (audit gap #3).

Verification

• RFC0018.4 green: event_name == "checkout" runs end-to-end via Querier::run_query → exactly the 2 matching rows (login + absent excluded); H6 holds (QueryResult is Ourios-owned).
• Full ourios-querier suite: 74+ tests pass, the new Field variant broke nothing (round-trip proptests, display, structured parse all green).
• cargo fmt --check, cargo clippy --all-targets clean.

RFC 0018 stays red overall — this greens 1 of 6 §5 scenarios. Remaining: .1/.2 (scope fields), .3 (retryable errors), .5 (non-finite doubles), .6 (severity preserve).

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@jensholdgaard, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 15 minutes and 39 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 0c0f8d07-018d-42dc-a04b-6edb56a2552d

📥 Commits

Reviewing files that changed from the base of the PR and between 39e769a and b528edf.

📒 Files selected for processing (6)

• crates/ourios-querier/src/compile.rs
• crates/ourios-querier/src/dsl/display.rs
• crates/ourios-querier/src/dsl/ir.rs
• crates/ourios-querier/src/dsl/parse.rs
• crates/ourios-querier/src/dsl/structured.rs
• crates/ourios-querier/tests/rfc0018_otlp_compliance.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/rfc0018-green-event-name

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Adds event_name as a first-class field in the ourios-querier logs DSL (RFC0018.4), wiring it through IR → parse/structured surfaces → display → compilation to the RFC0005 event_name column, and validating it end-to-end with a now-green acceptance test.

Changes:

• Introduces Field::EventName in the DSL IR and marks it as string-compatible for string calls.
• Teaches both the string DSL parser and the structured (JSON) surface to recognize event_name, and ensures canonical rendering outputs event_name.
• Extends query compilation to map event_name to the RFC0005 event_name column and adds a green RFC0018.4 integration test proving filtering works against a real Parquet store.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
crates/ourios-querier/tests/rfc0018_otlp_compliance.rs	Converts RFC0018.4 from ignored stub to a tokio end-to-end test asserting event_name filtering returns exactly the matching rows.
crates/ourios-querier/src/dsl/structured.rs	Adds "event_name" → Field::EventName mapping for the structured query surface.
crates/ourios-querier/src/dsl/parse.rs	Adds event_name to bare-field parsing and leak-free field naming for errors.
crates/ourios-querier/src/dsl/ir.rs	Adds Field::EventName and includes it in string-operand eligibility.
crates/ourios-querier/src/dsl/display.rs	Ensures canonical serialization prints event_name.
crates/ourios-querier/src/compile.rs	Maps Field::EventName to columns::EVENT_NAME, treats it as a text field, and enables string calls on it.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.