Uploaded image for project: 'Go Driver'
  1. Go Driver
  2. GODRIVER-2619

Allow application to have continued access to for ChangeStream.Current without extra copy

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None

    Description

      Currently if applications want to have continued access to ChangeStream.Current after calling Next/TryNext, they have to make a copy of it. This is every inefficient for applications that usually get large change events, and continued access for change streams is very common, for example putting the current event to a queue for async processing. It seems that the reason we have to do this is because the ChangeStream.Current slice can be overwritten, so this ticket is to improve the implementation to avoid applications doing extra copy.

      Attachments

        Activity

          People

            preston.vasquez@mongodb.com Preston Vasquez
            wenbin.zhu@mongodb.com Wenbin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: