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

Investigate possibility of adapting TransactionHistoryIterator for use in Change Streams

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: Aggregation Framework
    • None
    • Fully Compatible
    • Query 2019-03-11, Query 2019-04-22

      The TransactionHistoryIterator has the right interface for the prepared transaction lookups that we need in a Change Stream, but it uses the DBDirectClient, which may turn out to be impractical for use in an aggregation pipeline.

      It may be possible to make the TransactionHistoryIterator more widely usable by replacing the DBDirectClient call with a call to MongoProcessInterface::lookupSingleDocument(), which is the interface used by DocumentSourceLookupChangePostImage.

      Alternatively, we may decide to factor out the code for writing the query so that even if the Change Stream wants to use its own method for talking to the database, it can at least reuse the query-writing logic.

            Assignee:
            justin.seyster@mongodb.com Justin Seyster
            Reporter:
            justin.seyster@mongodb.com Justin Seyster
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: