GraphQL Mesh OData Handler currently assumes all paths implied by the $metadata are supported.
It has logic to inject $expand in order to span relationships, but that is disabled by default because it is not supported in many places.
The GraphQL Mesh OData Handler would be much more reliable and performant if it used the capabilities advertised by an OData/RAPID service both to limit the functionality exposed and to optimize what logic (like $expand) it could push to the store.
GraphQL Mesh OData Handler currently assumes all paths implied by the $metadata are supported.
It has logic to inject $expand in order to span relationships, but that is disabled by default because it is not supported in many places.
The GraphQL Mesh OData Handler would be much more reliable and performant if it used the capabilities advertised by an OData/RAPID service both to limit the functionality exposed and to optimize what logic (like $expand) it could push to the store.