IharYakimush

Hi, Retry feature is obsolete, I would not recommend to retry entire request. Instead use retry in particular place where transient fault can occurs. For instance: - EF Core -...

Hi Antonio, I checked "StructuralTypeConfiguration" class and it looks like there is no settings which can help in this case. You have to avoid recursion. Ihar

Hi Antonio, I think you can try to do small POC before building full model.

"In" logical operator is part of OData 4.01 (http://docs.oasis-open.org/odata/odata/v4.01/csprd02/part2-url-conventions/odata-v4.01-csprd02-part2-url-conventions.html). Current project support only OData 4.0. It should throw `ODataException` with message about "Syntax error". It looks like you using `Microsoft.OData.Core`...

Hi @kvpt , please add unit tests

Hi @chadcampbell , ServiceProvider is public, so you can dispose it if you want as a workaround. Regarding implementing `IDisposable` for the `ODataQuery` to dispose ServiceProvider: I need some time...

Also memory leak and CPU usage spike is not the same, so could you please provide some details about how you identified an issue. If you have some sample code...

Hi @mgesc , Filter in expand and expand itself applicable for collections. In your sample you trying to expand and filter single property "URLT" declared as `public virtual URLT URLT...

**Workaround:** 1. Create a class with a default constructor that implements the `IQueryable` interface. Implementation is not needed. ``` using System.Collections; using System.Linq.Expressions; namespace HotChocolateReproduction; public class QueryWorkaround : IQueryable...