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

Have UnorderedFastKeyTable iterators error if the table had been modified.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Gone away
    • None
    • None
    • Internal Code
    • None

    Description

      There isn't a clearly defined behavior of how modifications done to an UnorderedFastKeyTable will affect what values a scanning iterator will observe. SERVER-32532 is an example of where the iterator is expecting to observe all items in the map, but due to underlying function calls erasing and adding items back in, the required behavior is not achieved.

      I apologize that this ticket isn't proposing a complete specification, but I believe at the very least, moving and accessing an iterator should cause a crash (debug mode only?) if the underlying map has had items both removed and added since the iterator's creation. That would have been sufficient for surfacing SERVER-32532.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-platform DO NOT USE - Backlog - Platform Team
              daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: