Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-94005

Investigate query settings path for a query on _id

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution

      In the code where we look up the query settings for a find command here, we return an empty query settings object for IDHACK queries and we call 'isIdHackEligibleQueryWithoutCollator' to determine if the query is an IDHACK query. This may be a problem for a query that has a collation that is different from the collection's collation - in order for a query to be eligible for IDHACK, the query's collation must match the collection's collation. So if we tried to get the query settings for a query like that we would erroneously return an empty query settings object when maybe there was something to return. Perhaps we should also be checking collation here by calling 'isIdHackEligibleQuery' instead?

            Assignee:
            Unassigned Unassigned
            Reporter:
            militsa.sotirova@mongodb.com Militsa Sotirova
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: