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

Support different allocators for SortedDataKeyValueView::getValueCopy()

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • RSS Sydney

      We can allow users to select how the memory should be managed by using key_string::Builder / key_string::HeapBuilder / key_string::PooledBuilder depending on the needs. Right now getValueCopy() just calls key_string::Value::makeValue() to create a Value. This function is indirectly called from nextKeyString() and seekForKeyString().

      The context is in this PR.

            Assignee:
            Unassigned Unassigned
            Reporter:
            wei.hu@mongodb.com Wei Hu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: