Investigate factoring out PartitionIterator partition comparison code

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Query Optimization 2021-06-14
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      Its possible that we could share partition key comparision code with the PartitionIterator to optimize memory usage in the non-full cases. Since we're sorting by

      {partitionFields, densifyField}

      we can throw away data from previous partitions once we've seen a value from the next partition.

            Assignee:
            Ted Tuckman
            Reporter:
            Joe Kanaan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: