Node query pattern & partial response with DGS

[dusinof]

Hi Everyone,

we are trying to use GraphQL node query pattern with DGS to obtain a partial response for nodes query.
Let's use this schema:

type Query {

    "Get node by id"
    node(id: ID!): Node

    "Get nodes by ids"
    nodes(ids: [ID!]!): [Node]
}

interface Node{
    id: ID!
}

type Car implements Node {
    id: ID!
    color: String!
    year: Int!

}

So we have a node interface and some actual graphql objects that implement this interface. For example Car in our case.
Node query is not a problem. It returns data or error
The nodes query doesn't work as expected because it also returns data or error but we want partial response meaning data & error

Assume, that in our Database we have the following cars: ["Mazda", "Toyota", "Opel"] we do not have BMW.

When we run the query:

query demoCar{
	 nodes(ids: ["Mazda", "Toyota", "BMW"]) {
			... on Car {
				__typename
				id
				color
				year
			}
	}
}

Current Result

{
	"errors": [
		{
			"message": "Validation Failed With: BMW CAR_DOESNT_EXISTS",
			"locations": [
				{
					"line": 2,
					"column": 2
				}
			],
			"path": [
				"nodes"
			],
			"extensions": {
				"errorCode": "CAR_DOESNT_EXISTS",
				"classification": "DataFetchingException"
			}
		}
	],
	"data": {
		"nodes": null
	}
}

We used standard DGS Annotations for getting the nodes.

   @DgsQuery
   fun nodes(@InputArgument ids: List<String>): List<Node> {
      //Some logic to obtain a proper service and then the data
      return CarService.getNodesData(ids)
    }

When there is an exception during the execution of CarService.getNodesData(ids) then the whole response is data = null & errors contains details.
From my point of view, it makes sense, because in this case, nodes behave like field... and when the exception is thrown, it always contains data or null (the error block is filled with information).

Main Question

So how we can achieve a partial response in this case? We known, that DB returns only 2 Cars but query requested 3 cars. We want to return at least what we found, together with error detail.

Expected Behavior

When the exception is thrown during the nodes query, the exception handler is triggered, and processed, and the whole process continues until everything is processed and then the partial response is returned.

{
	"errors": [
		{
			"message": "Validation Failed With CAR_DOESNT_EXISTS",
			"locations": [
				{
					"line": 2,
					"column": 2
				}
			],
			"path": [
				"nodes"
			],
			"extensions": {
                "nodeID": "BMW"
				"errorCode": "CAR_DOESNT_EXISTS",
				"classification": "DataFetchingException"
			}
		}
	],
	"data": {
		"nodes": [
			{
				"__typename": "Car",
				"id": "Mazda",
				"color": "red",
				"year":2023
			},
			{
				"__typename": "Car",
				"id": "Toyota",
				"color": "white",
				"year":2024
			}
		]
	}
}

Basically same problem was asked here but also without resolution.
I found a resolution by using DataFetcherResult but it is not exactly what we are looking for, because in that case, everything has to be in try/catch and error part has to be constructed manually, and that isn't what we are looking for.

[momentary-lapse]

@dusinof I stumbled upon the same problem. Have you come across a suitable solution, per chance?