• Type: Icon: Epic Epic
    • Resolution: Done
    • Priority: Icon: Unknown Unknown
    • 2.21.0
    • Affects Version/s: None
    • Component/s: LINQ3, oData
    • None
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • Done
    • oData support for LINQ3
    • 5
    • 6
    • 6
    • 100
    • Hide

      Engineer: Alex

      2023-08-18: Project Completed

      • Project closed

      2023-08-08: Updated end date to 2023-08-11

      • Last PR in final stages of review. Should wrap up in the next few days

      2023-07-21: Updated end date to 2023-07-28

      • Being actively reviewed. Extended the end date for reviews to wrap up

      2023-07-07: Updated target end date to 2023-07-14

      Status Update:

      • Code is done, waiting on reviews
      • Working on setting up the CI build which is the last piece of work to wrap this up and should take a day or less to do

      2023-06-23: Updating target end date to 2023-06-30

      Status Update:

      • Code is ready for review. Waiting on finalizing a repo for it before putting it up for review officially
      • Currently working on improving the test coverage
      • Added another week to the end date to account for review time

      2023-06-08: Setting initial end date to 2023-06-30

      Status Update:

      • Support for $select and $expand will wrap up by the end of next week
      • Implementing different use cases and documentation will be up next

       

      Show
      Engineer: Alex 2023-08-18: Project Completed Project closed 2023-08-08: Updated end date to 2023-08-11 Last PR in final stages of review. Should wrap up in the next few days 2023-07-21: Updated end date to 2023-07-28 Being actively reviewed. Extended the end date for reviews to wrap up 2023-07-07: Updated target end date to 2023-07-14 Status Update: Code is done, waiting on reviews Working on setting up the CI build which is the last piece of work to wrap this up and should take a day or less to do 2023-06-23: Updating target end date to 2023-06-30 Status Update: Code is ready for review. Waiting on finalizing a repo for it before putting it up for review officially Currently working on improving the test coverage Added another week to the end date to account for review time 2023-06-08: Setting initial end date to 2023-06-30 Status Update: Support for $select and $expand will wrap up by the end of next week Implementing different use cases and documentation will be up next  

      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.

            Assignee:
            oleksandr.poliakov@mongodb.com Oleksandr Poliakov
            Reporter:
            james.kovacs@mongodb.com James Kovacs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              10 weeks, 3 days