-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add tracing for SplitManager.getSplits #20194
Add tracing for SplitManager.getSplits #20194
Conversation
Sometimes, `ConnectorSplitManager.getSplits` can take long to construct `ConnectorSplitSource`. For example, in Delta, there is IO work being done before `ConnectorSplitSource` is returned. This work would better be delayed until `ConnectorSplitSource.getNextBatch` is invoked, but currently this is not the case. Let's add tracing so that time spent in `ConnectorSplitManager.getSplits` is attributable.
The parameter refers to "a stage span", not to the top level "query span".
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.
cc @romanvainb
cc: @lukasz-stec were we thinking about similar for PageSourceProvider for system tables? |
thanks @wendigo for restarting the failed builds |
@hashhar I wasn't thinking about that but yes, it looks useful. That said tracing is already there for most of stuff via TracingMetadata, it just not linked to the parent span correctly I believe. |
Sometimes,
ConnectorSplitManager.getSplits
can take long to constructConnectorSplitSource
. For example, in Delta, there is IO work being done beforeConnectorSplitSource
is returned. This work would better be delayed untilConnectorSplitSource.getNextBatch
is invoked, but currently this is not the case. Let's add tracing so that time spent inConnectorSplitManager.getSplits
is attributable.