-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Dont call multiunzip when no stats #9220
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
Dont call multiunzip when no stats #9220
Conversation
| .unwrap(); | ||
| c.bench_function(&format!("physical_plan_tpch_{}", q), |b| { | ||
| b.iter(|| logical_plan(&ctx, &sql)) | ||
| b.iter(|| physical_plan(&ctx, &sql)) |
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.
There was disconnect between benchmark name (physical plan) and the function(logical plan), so I corrected this
alamb
left a comment
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.
Thank you @matthewmturner and @Dandandan
| all_files: impl Stream<Item = Result<(PartitionedFile, Statistics)>>, | ||
| file_schema: SchemaRef, | ||
| limit: Option<usize>, | ||
| collect_stats: bool, |
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.
Given the function is called 'get_statisticsand now there is a boolean flag that implies the stats aren't collected, can we please add some documentation to the docstring explaining what thecollect_stats` flag does?
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.
Yes good catch, will do.
|
@alamb I have updated the docstring. let me know if anything else |
|
Thanks again @matthewmturner ! |
Which issue does this PR close?
Closes #9219
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?