Unknown Summary
Users are reporting bugs and missing features when trying to use LINQ3 with oData. We should consider investing in oData-related testing to ensure common oData LINQ queries can be executed with LINQ3.
Motivation
Who is the affected end user?
Users creating oData endpoints backed by MongoDB.
How does this affect the end user?
Common oData queries often do not work because of ExpressionNotSupportedExceptions or serialization problems.
How likely is it that this problem or use case will occur?
Users attempting to use oData with our LINQ3 provider quickly hit blockers. Our LINQ2 provider did not work with oData at all.
If the problem does occur, what are the consequences and how severe are they?
Historically oData has not worked with our LINQ providers as we have not invested in supporting oData. Given that query generation is handled by oData itself, users are left with few to no options beyond using a different database and LINQ provider with better oData support.
Is this issue urgent?
This only affects users wanting to use oData with the .NET/C# driver.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
No.