rtk-ai/rtk

Feature request: filter for `bq` (BigQuery CLI)

Open

#1,707 opened on May 4, 2026

View on GitHub
 (2 comments) (1 reaction) (0 assignees)Rust (2,914 forks)batch import
area:clienhancementhelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Command

bq query, bq ls, bq show, bq (generic)

Usage frequency (from rtk discover)

  • bq query: 684x
  • bq (generic): 334x
  • bq ls: 133x
  • bq show: 99x
  • Total: ~1,250 invocations

Why it matters

BigQuery CLI output is very verbose — bq query returns full JSON result sets, bq show dumps full table schemas with statistics, bq ls lists datasets/tables with metadata. Most of this content is noise for the LLM.

Suggested filter behavior

  • bq query: keep column headers + first N rows, strip jobComplete, totalRows, cacheHit, schema wrapper noise
  • bq ls: keep table/dataset names only, strip creationTime, lastModifiedTime, numBytes, numRows
  • bq show: keep schema field names + types only, strip tableReference, statistics, encryptionConfiguration

Environment

GCP / BigQuery CLI (google-cloud-sdk)

Contributor guide

Research direction
Examine the existing output processing pipeline in rtk for CLI commands, then implement trimming logic for bq output as specified: strip verbose headers, wrappers, and metadata, keeping only essential data for LLM consumption.
Tech stack
rust
Domain
clibackend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCLI development basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75