-
Notifications
You must be signed in to change notification settings - Fork 7
More profile metrics for Iceberg, S3 and Azure #1123
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: antalya-25.8
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -20,6 +20,7 @@ | |
| #include <Processors/QueryPlan/ReadFromSystemNumbersStep.h> | ||
| #include <Storages/ObjectStorage/DataLakes/DataLakeConfiguration.h> | ||
| #include <Storages/ObjectStorage/DataLakes/Iceberg/IcebergMetadata.h> | ||
| #include <Storages/ObjectStorage/DataLakes/Iceberg/IcebergWrites.h> | ||
| #include <Storages/ObjectStorage/StorageObjectStorage.h> | ||
| #include <Storages/SelectQueryInfo.h> | ||
| #include <base/Decimal.h> | ||
|
|
@@ -83,7 +84,7 @@ void IcebergMetadataLogElement::appendToBlock(MutableColumns & columns) const | |
|
|
||
| void insertRowToLogTable( | ||
| const ContextPtr & local_context, | ||
| String row, | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That needs a comment that explains WHY we need NOT a value, but a function here... do I get it right that major reason is not to skew the the time measurements by getting metadata content?
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. To make |
||
| std::function<String()> get_row, | ||
| IcebergMetadataLogLevel row_log_level, | ||
| const String & table_path, | ||
| const String & file_path, | ||
|
|
@@ -103,7 +104,7 @@ void insertRowToLogTable( | |
| .content_type = row_log_level, | ||
| .table_path = table_path, | ||
| .file_path = file_path, | ||
| .metadata_content = row, | ||
| .metadata_content = get_row(), | ||
| .row_in_file = row_in_file}); | ||
| } | ||
| } | ||
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.
Perhaps putting it in a scope will be more accurate and safer (e.g, future changes to this method that introduce slow operations could lead to wrong values)?
Example:
The same comment applies to the other list object operations.
In any case, I see that it is already implemented without this "protection". So it is not a must to implement this 👍
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.
You are right, I want to get time for S3/Azure communication, not for parsing for response.