Expose table column usage in query context#135
Open
ei-grad wants to merge 1 commit into
Open
Conversation
Parse the colsUsed and colsUsedBitset fields that osquery core already serializes into table plugin request contexts. Expose them on QueryContext and add helpers so table generators can avoid populating expensive columns when SQLite does not need them. This keeps older contexts conservative by treating missing column-usage metadata as all columns potentially used. It addresses aggregate queries that only need grouping columns but previously forced Go extensions to emit large complete rows before SQLite aggregation. Refs: osquery#134 Co-Authored-By: Codex CLI <noreply@openai.com>
|
|
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
Why
osquery core already serializes projection metadata for table plugins, but osquery-go discarded it. Go extension tables with large or expensive columns then have to emit complete rows even for aggregate queries that only need grouping columns. This can hit Thrift message limits before SQLite applies aggregation.
Fixes #134
Tests
Prepared with LM assistance — Codex CLI