-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Physical operator logging #17752
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
Physical operator logging #17752
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.
Looks great!
@Mytherin Sam and I are happy with the way this looks right now but maybe you want to have a look as well. Sam commented that the current I could see us using a
EDIT: or maybe add the
|
@lnkuiper Yea that sounds good to me! |
Sounds good to me. Is this ready to merge? |
@Mytherin I'll make the change I came up with in my comment to make the log entries slightly more structured. I'll mark ready to merge when I'm done! |
Thanks! |
Physical operator logging (duckdb/duckdb#17752)
Physical operator logging (duckdb/duckdb#17752) Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
Very basic initial implementation. Adds a new log type (
PhysicalOperator
) and adds logging for the hash join and parquet writer. I've implemented a utility that can be passed into classes that we use during execution such asJoinHashTable
andParquetWriter
that logs messages, but we can see which operator this belongs to:I'd be happy to receive any feedback on this :)