OrderBy with RedisCollection<T> as IQueryable<T> using OData

[mfaulcon]

I see in the code that SearchExtensions.cs defines an OrderBy method on the IRedisCollection interface (among others):

redis-om-dotnet/src/Redis.OM/SearchExtensions.cs

Line 545 in 7f43b7b

public static IRedisCollection<T> OrderBy<T, TField>(this IRedisCollection<T> source, Expression<Func<T, TField>> expression)

However, I'm trying to use RedisOM with OData as an IQueryable data source, and OData is sending an OrderBy expression that ultimately is making it to the RedisQueryProvider.(Expression expression) method, which doesn't.

redis-om-dotnet/src/Redis.OM/Searching/RedisQueryProvider.cs

Line 261 in 7f43b7b

public TResult? Execute<TResult>(Expression expression)

Before I spend time trying to figure out how to make that work, is this a known problem with trying to use RedisOM with OData? Is there a workaround? If not, is this something that is going to be relatively easy to accomplish, or am I barking up the wrong tree?

[mfaulcon]

Update:

I think this is less an OrderBy problem, and more an OData issue. Here's the expression it passed to RedisOM:

value(
  Redis.OM.Searching.RedisCollection`1[Graph.Caching.RedisOM.Users.CachedUser])
    .OrderBy(x => x.UserId)
    .Take(value(
      Microsoft.AspNetCore.OData.Query.Container.LinqParameterContainer+TypedLinqParameterContainer`1[System.Int32])
      .TypedProperty)

Not sure why its coming through this way...

[slorello89]

@mfaulcon - can you provide me a minimal reproduction of the issue you are seeing?

[mfaulcon]

Upon further investigation, this issue is overtaken by #518 - I did not trace the original issue down deeply enough; my apologies.

Closing...