AspNetCoreOData

AspNetCoreOData copied to clipboard

During serialization, we create an `ODataResource` for every resource and nested resource that we write. This process is expensive, costs 20%+ CPU in most profiles I've taken. The [`ODataResourceSerializer.CreateResource`](https://github.com/OData/AspNetCoreOData/blob/main/src/Microsoft.AspNetCore.OData/Formatter/Serialization/ODataResourceSerializer.cs#L510) does...

habbes

Perf: Creating OData properties is expensive

3

During serialization, a relatively high amount of CPU is used to create `ODataProperty` instances that are used to populate `ODataResource` objects. This is performed in the [`ODataSerializerPropertyHelper.CreateProperty`](https://github.com/OData/AspNetCoreOData/blob/main/src/Microsoft.AspNetCore.OData/Formatter/Serialization/ODataSerializerPropertyHelper.cs#L27) method. The most...

habbes

Incorrect Handling of DELETE Request with $each path segment

6

**Assemblies affected** ASP.NET Core OData 8.2.3 **Describe the bug** When attempting to make a DELETE request to delete members of a collection using the $each segment in an OData controller,...

Supernectar

Cast segment after navigation property not supported conventionally

1

We currently support the following routes conventionally via the `PropertyRoutingConvention`: - `{entityset}({key})/{structuralproperty}/{cast}` or `{entityset}/{key}/{structuralproperty}/{cast}` - `{singleton}/{structuralproperty}/{cast}` Where, - `structuralproperty` can be single-valued or collection-valued - the route is matched to...

gathogojr

Model Validation Not Automatically Applied in OData Controller

7

**Assemblies affected** ASP.NET Core OData 8.2.3 **Describe the bug** The OData controller, specifically the CustomersController, is not automatically applying model validation to the key parameter in the Delete endpoint, despite...

Supernectar

Given "Microsoft.AspNetCore.OData" Version="8.2.3" and async OData controller: [EnableQuery] public async Task Get() { IQueryable queryable = _context.Orders; return queryable.AsAsyncEnumerable(); } When I execute a query then I see 2 separate...

kerajel

Adding Odata in Versioning breaks the ability to perform select, filter etc. and Removing that breaks the swagger versioning

8

**Assemblies affected** ``` ``` **Describe the bug** I have setup following ``` services.AddControllers() .AddOData((opt) => { opt.EnableQueryFeatures() .AddRouteComponents("api/V1", GetEdmModelV1()) .AddRouteComponents("api/V2", GetEdmModelV2()); }); ``` and then ``` services.AddApiVersioning() // Core API...

akshaybheda

Odata Response in API with high volume of data from multiple tables

4

**Assemblies affected** net6.0 Microsoft.AspNetCore.OData" Version="8.0.10" Microsoft.EntityFrameworkCore Version="6.0.0" Odata works good when data is fetching from single tables eg Person, Author etc Its features like $count,select,$filter,$top,$skip works fine. I have a...

DevDavee

Unable to override location in response header.

9

**Assemblies affected** ASP.NET Core OData 8.2.0 **Describe the bug** We want to add specific url in location response header, but we are unable to override. I looked into the code...

ishatyagiit

PageSize attribute causes significant drop in throughput

3

**Assemblies affected** AspNetCoreOData 7.5.17; ODataLib 7.13.0, .NET Core 3.1 **Describe the bug** A customer is experiencing a significant throughput in WebAPI when using PageSize. The throughput drops from 400k+ rps...

habbes