4 data loader requests with 4 customised data loader classes, but with the same key

[SnigdhaSanat]

I am using com.graphql-java:java-dataloader: version 3.3.0. I have a scenario whew the graphql request is something of the shape:

query myQuery($id: ID!) {
  node(id: $id) {
    id
    ... on myObject {
      name
      
      field1 {
        totalCount
      }
      field2 {
        totalCount
      }
      field3 {
        totalCount
      }
      field4 {
        totalCount
      }
    }
  }
}

I have 4 classes that extend DataLoader, to resolve field1 to field4. Each of them use the same key id. I don't see the DataLoader's batchLoadFunction function getting executed for any of the 4 calls to dataloader.load()

Is this behaviour expected? Also, did something changed between the above version 3.3.0 and a previous version 3.1.2?

[bbakerman]

Sorry you have not provided enough information to help debug this. A simple reproduction of the issue would be best.

One thing that stands out is you said I have 4 classes that extend DataLoader, to resolve field1 to field4. I would not expect that you have to extend DataLoader at all. What new functionality did you add?

Also it seems to imply you need a custom DataLoader class per field. That also seems strange.

[github-actions]

Hello, this issue has been inactive for 60 days, so we're marking it as stale. If you would like to continue this discussion, please comment within the next 30 days or we'll close the issue.