You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be one span for each "read batch" and one scan for each "read file". The batch spans should be children of the file span.
If possible it would be nice if the "read file" spans were children of the exec plan when the scanner is being used as a source node. I'm not sure if this is doable though since the scanner is often used outside the exec plan.
David Li / @lidavidm:
Hmm, we could add a "parent span" or properly "parent span context" option to the scanner options. (That way you could link it up to a Flight span or something too.) You'd have to manually inject it to spans started in the scanner, though. (~2 lines of code or so for each span)
There should be one span for each "read batch" and one scan for each "read file". The batch spans should be children of the file span.
If possible it would be nice if the "read file" spans were children of the exec plan when the scanner is being used as a source node. I'm not sure if this is doable though since the scanner is often used outside the exec plan.
Reporter: Weston Pace / @westonpace
Assignee: Joost Hoozemans / @joosthooz
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-15067. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: