Skip to content

Conversation

PascalSenn
Copy link
Contributor

No description provided.

Comment on lines +171 to +172
The span SHOULD be a child of the span that initiated the batch loading,
which is typically a resolver execution span.
Copy link
Contributor

@EmrysMyrddin EmrysMyrddin Sep 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You probably already discussed this during the meeting, but I'm not sure to understand this part.

What does "initiated the batch loading" ? Is it the last or the first resolver that called this DataLoader ?

And this means that other resolvers spans will not have anything to do with this span. Should we specify that the DataLoader span should be linked to every resolver spans involved in the batch ? Because a common need is to being able to track down which resolver triggered a DataLoader batch.

The span SHOULD be a child of the span that initiated the batch loading,
which is typically a resolver execution span.
attributes:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that would be useful to also know the number of cache miss/hit isn't it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants