-
Couldn't load subscription status.
- Fork 118
feat: Inspect table fixes #1372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@scovich I'm curious about the variant schema stuff. Is that meant to help with the performance issues we've been seeing? |
| fn custom_log_schema() -> SchemaRef { | ||
| let fields = get_log_schema() | ||
| .fields() | ||
| .filter(|f| f.name() != "commitInfo") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a follow-up to actually support reading commit infos as I imagine that could be something useful to dump from a table.
What changes are proposed in this pull request?
The
inspect-tableexample had rotted and was not runnable. It also lacked domain metadata support.Additionally, upgrade the example's
actionscommand with a--stats-onlyflag that avoids materializing file actions.The command now unconditionally emits stats such as the following:
If
--stats-onlywas not supplied, the stats are followed by a complete printout of log actions, as before.How was this change tested?
Example code now runs nicely.