Skip to content

feat: trace schema planning#151

Merged
mag1cfrog merged 3 commits into
mainfrom
feat/143-schema-planning-tracing
Jun 23, 2026
Merged

feat: trace schema planning#151
mag1cfrog merged 3 commits into
mainfrom
feat/143-schema-planning-tracing

Conversation

@mag1cfrog

Copy link
Copy Markdown
Owner

Summary

Closes #143.

Adds stable structured tracing around Arrow-to-SQL Server schema planning without changing planning semantics or public API behavior.

Changes

  • Add stable schema planning phase, span, and event marker names.
  • Emit schema planning start, successful completion, and failure events.
  • Record field count, mapping count, diagnostic counts, profile fields, policy fields, and elapsed time.
  • Record diagnostic codes and diagnostic field names for failure summaries.
  • Record low-cardinality Arrow and MSSQL type family summaries on successful planning.
  • Keep sensitive schema metadata and timezone strings out of tracing fields.

Safety

  • Does not emit row values.
  • Does not emit schema metadata values.
  • Does not emit full Arrow DataType debug strings.
  • Does not emit arbitrary SQL text, connection strings, passwords, or tokens.
  • Does not install a global subscriber.

Validation

  • cargo fmt --all --check
  • cargo test -p arrow-tiberius schema::table_mapping
  • cargo check --workspace
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test --workspace
  • git diff --check main...HEAD

@mag1cfrog mag1cfrog merged commit 4886892 into main Jun 23, 2026
3 of 4 checks passed
@mag1cfrog mag1cfrog deleted the feat/143-schema-planning-tracing branch June 23, 2026 02:03
@mag1cfrog mag1cfrog self-assigned this Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Observability: trace Arrow to SQL Server schema planning

1 participant