Sort-merge join: Difference between revisions
No edit summary |
|||
(24 intermediate revisions by 17 users not shown) | |||
Line 1: | Line 1: | ||
{{Short description|Algorithm used in relational databases}} |
|||
{{Unreferenced|date=December 2009}} |
|||
The '''sort-merge join''' (also known as merge |
The '''sort-merge join''' (also known as merge join) is a [[join algorithm]] and is used in the implementation of a [[relational database|relational]] [[database management system]]. |
||
The basic problem of a join algorithm is to find, for each distinct value of the join attribute, the set of [[tuple]]s in each relation which display that value. The key idea of the |
The basic problem of a join algorithm is to find, for each distinct value of the join attribute, the set of [[tuple]]s in each relation which display that value. The key idea of the sort-merge algorithm is to first sort the relations by the join attribute, so that interleaved linear scans will encounter these sets at the same time. |
||
In practice, the most expensive part of performing a sort-merge join is arranging for both inputs to the algorithm to be presented in sorted order. This can be achieved via an explicit sort operation (often an [[external sort]]), or by taking advantage of a pre-existing ordering in one or both of the join relations. The latter condition can occur because an input to the join might be produced by an index scan of a tree-based index, another merge join, or some other plan operator that happens to produce output sorted on an appropriate key. |
In practice, the most expensive part of performing a sort-merge join is arranging for both inputs to the algorithm to be presented in sorted order. This can be achieved via an explicit sort operation (often an [[external sort]]), or by taking advantage of a pre-existing ordering in one or both of the join relations.<ref>{{Cite web |title=Sort-Merge Joins |url=https://www.dcs.ed.ac.uk/home/tz/phd/thesis/node20.htm |access-date=2022-11-02 |website=www.dcs.ed.ac.uk}}</ref> The latter condition, called interesting order, can occur because an input to the join might be produced by an index scan of a tree-based index, another merge join, or some other plan operator that happens to produce output sorted on an appropriate key. Interesting orders need not be serendipitous: the optimizer may seek out this possibility and choose a plan that is suboptimal for a specific preceding operation if it yields an interesting order that one or more downstream nodes can exploit. |
||
== Complexity == |
|||
Let's say that we have two relations <math>R</math> and <math>S</math> and <math> |R|<|S| </math>. <math>R</math> fits in <math>P_{r}</math> pages memory and <math>S</math> fits in <math>P_{s}</math> pages memory. So, in the worst case '''Sort-Merge Join''' will run in <math>O(P_{r}+P_{s})</math> I/Os. In the case that <math>R</math> and <math>S</math> are not ordered the worst case time cost will contain additional terms of sorting time: <math>O(P_{r}+P_{s}+P_{r}\log(P_{r})+ P_{s}\log(P_{s}))</math>, which equals <math>O(P_{r}\log(P_{r})+ P_{s}\log(P_{s}))</math> (as [[linearithmic time|linearithmic]] terms outweigh the linear terms, see [[Big O notation#Orders of common functions|Big O notation – Orders of common functions]]). |
|||
Let <math>R</math> and <math>S</math> be relations where <math> |R|<|S| </math>. <math>R</math> fits in <math>P_{r}</math> pages memory and <math>S</math> fits in <math>P_{s}</math> pages memory. In the worst case, a '''sort-merge join''' will run in <math>O(P_{r}+P_{s})</math> I/O operations. In the case that <math>R</math> and <math>S</math> are not ordered the worst case time cost will contain additional terms of sorting time: <math>O(P_{r}+P_{s}+P_{r}\log(P_{r})+ P_{s}\log(P_{s}))</math>, which equals <math>O(P_{r}\log(P_{r})+ P_{s}\log(P_{s}))</math> (as [[linearithmic time|linearithmic]] terms outweigh the linear terms, see [[Big O notation#Orders of common functions|Big O notation – Orders of common functions]]). |
|||
==Pseudocode== |
==Pseudocode== |
||
For simplicity, the algorithm is described in the case of an [[Join_(SQL)#Inner_join|inner join]] of two relations |
For simplicity, the algorithm is described in the case of an [[Join_(SQL)#Inner_join|inner join]] of two relations ''left'' and ''right''. Generalization to other join types is straightforward. The output of the algorithm will contain only rows contained in the ''left'' and ''right'' relation and duplicates form a [[Cartesian product]]. |
||
<syntaxhighlight lang="typescript"> |
|||
'''function''' sortMerge('''relation''' left, '''relation''' right, '''attribute''' a) |
|||
function Sort-Merge Join(left: Relation, right: Relation, comparator: Comparator) { |
|||
'''var relation''' output |
|||
result = new Relation() |
|||
'''var list''' left_sorted := sort(left, a) ''// Relation left sorted on attribute a'' |
|||
'''var list''' right_sorted := sort(right, a) |
|||
// Ensure that at least one element is present |
|||
'''var attribute''' left_key, right_key |
|||
if (!left.hasNext() || !right.hasNext()) { |
|||
'''var set''' left_subset, right_subset ''// These sets discarded except where join predicate is satisfied'' |
|||
return result |
|||
advance(left_subset, left_sorted, left_key, a) |
|||
} |
|||
advance(right_subset, right_sorted, right_key, a) |
|||
'''while not''' empty(left_subset) '''and not''' empty(right_subset) |
|||
// Sort left and right relation with comparator |
|||
'''if''' left_key = right_key ''// Join predicate satisfied'' |
|||
left.sort(comparator) |
|||
add cartesian product of left_subset and right_subset to output |
|||
right.sort(comparator) |
|||
advance(left_subset, left_sorted, left_key, a) |
|||
advance(right_subset, right_sorted, right_key, a) |
|||
// Start Merge Join algorithm |
|||
'''else if''' left_key < right_key |
|||
leftRow = left.next() |
|||
advance(left_subset, left_sorted, left_key, a) |
|||
rightRow = right.next() |
|||
'''else''' ''// left_key > right_key'' |
|||
advance(right_subset, right_sorted, right_key, a) |
|||
outerForeverLoop: |
|||
'''return''' output |
|||
while (true) { |
|||
while (comparator.compare(leftRow, rightRow) != 0) { |
|||
if (comparator.compare(leftRow, rightRow) < 0) { |
|||
// Left row is less than right row |
|||
if (left.hasNext()) { |
|||
// Advance to next left row |
|||
leftRow = left.next() |
|||
} else { |
|||
break outerForeverLoop |
|||
} |
|||
} else { |
|||
// Left row is greater than right row |
|||
if (right.hasNext()) { |
|||
// Advance to next right row |
|||
rightRow = right.next() |
|||
} else { |
|||
break outerForeverLoop |
|||
} |
|||
} |
|||
} |
|||
// Mark position of left row and keep copy of current left row |
|||
left.mark() |
|||
markedLeftRow = leftRow |
|||
while (true) { |
|||
while (comparator.compare(leftRow, rightRow) == 0) { |
|||
// Left row and right row are equal |
|||
// Add rows to result |
|||
result = add(leftRow, rightRow) |
|||
// Advance to next left row |
|||
leftRow = left.next() |
|||
// Check if left row exists |
|||
if (!leftRow) { |
|||
// Continue with inner forever loop |
|||
break |
|||
} |
|||
} |
|||
if (right.hasNext()) { |
|||
// Advance to next right row |
|||
rightRow = right.next() |
|||
} else { |
|||
break outerForeverLoop |
|||
} |
|||
if (comparator.compare(markedLeftRow, rightRow) == 0) { |
|||
// Restore left to stored mark |
|||
left.restoreMark() |
|||
leftRow = markedLeftRow |
|||
} else { |
|||
// Check if left row exists |
|||
if (!leftRow) { |
|||
break outerForeverLoop |
|||
} else { |
|||
// Continue with outer forever loop |
|||
break |
|||
} |
|||
} |
|||
} |
|||
} |
|||
return result |
|||
} |
|||
</syntaxhighlight> |
|||
Since the comparison logic is not the central aspect of this algorithm, it is hidden behind a generic comparator and can also consist of several comparison criteria (e.g. multiple columns). The compare function should return if a row is ''less(-1)'', ''equal(0)'' or ''bigger(1)'' than another row: |
|||
''// Remove tuples from sorted to subset until the sorted[1].a value changes'' |
|||
'''function''' advance(subset '''out''', sorted '''inout''', key '''out''', a '''in''') |
|||
<syntaxhighlight lang="typescript"> |
|||
key := sorted[1].a |
|||
function compare(leftRow: RelationRow, rightRow: RelationRow): number { |
|||
subset := '''emptySet''' |
|||
// Return -1 if leftRow is less than rightRow |
|||
'''while not''' empty(sorted) '''and''' sorted[1].a = key |
|||
// Return 0 if leftRow is equal to rightRow |
|||
insert sorted[1] into subset |
|||
// Return 1 if leftRow is greater than rightRow |
|||
remove sorted[1] |
|||
} |
|||
</syntaxhighlight> |
|||
Note that a relation in terms of this pseudocode supports some basic operations: |
|||
<syntaxhighlight lang="typescript"> |
|||
interface Relation { |
|||
// Returns true if relation has a next row (otherwise false) |
|||
hasNext(): boolean |
|||
// Returns the next row of the relation (if any) |
|||
next(): RelationRow |
|||
// Sorts the relation with the given comparator |
|||
sort(comparator: Comparator): void |
|||
// Marks the current row index |
|||
mark(): void |
|||
// Restores the current row index to the marked row index |
|||
restoreMark(): void |
|||
} |
|||
</syntaxhighlight> |
|||
==Simple C# |
==Simple C# implementation== |
||
Note that this implementation assumes the join attributes are unique, i.e., there is no need to output multiple tuples for a given value of the key. |
Note that this implementation assumes the join attributes are unique, i.e., there is no need to output multiple tuples for a given value of the key. |
||
< |
<syntaxhighlight lang="csharp"> |
||
public class MergeJoin |
public class MergeJoin |
||
{ |
{ |
||
// Assume that left and right are already sorted |
// Assume that left and right are already sorted |
||
public static Relation |
public static Relation Merge(Relation left, Relation right) |
||
{ |
{ |
||
Relation output = new Relation(); |
Relation output = new Relation(); |
||
while (!left.IsPastEnd |
while (!left.IsPastEnd && !right.IsPastEnd) |
||
{ |
{ |
||
if (left.Key == right.Key) |
if (left.Key == right.Key) |
||
Line 70: | Line 161: | ||
public int position = 0; |
public int position = 0; |
||
public int Position |
public int Position => position; |
||
{ |
|||
get { return position; } |
|||
} |
|||
public int Key |
public int Key => list[position]; |
||
{ |
|||
public bool IsPastEnd => position == ENDPOS; |
|||
get { return list[position]; } |
|||
} |
|||
public bool Advance() |
public bool Advance() |
||
Line 94: | Line 181: | ||
{ |
{ |
||
list.Add(key); |
list.Add(key); |
||
} |
|||
public bool IsPastEnd() |
|||
{ |
|||
return position == ENDPOS; |
|||
} |
} |
||
Line 117: | Line 199: | ||
} |
} |
||
} |
} |
||
</syntaxhighlight> |
|||
</source> |
|||
==See also== |
|||
*[[Hash join]] |
|||
*[[Nested loop join]] |
|||
== References == |
|||
{{Reflist}} |
|||
==External links== |
==External links== |
||
[http://www.necessaryandsufficient.net/2010/02/join-algorithms-illustrated/ C# Implementations of Various Join Algorithms] |
|||
{{DEFAULTSORT:Sort-Merge Join}} |
{{DEFAULTSORT:Sort-Merge Join}} |
||
[[Category:Join algorithms]] |
[[Category:Join algorithms]] |
||
[[Category:Articles with example pseudocode]] |
|||
[[Category:Articles with example C Sharp code]] |
Latest revision as of 08:29, 25 October 2024
The sort-merge join (also known as merge join) is a join algorithm and is used in the implementation of a relational database management system.
The basic problem of a join algorithm is to find, for each distinct value of the join attribute, the set of tuples in each relation which display that value. The key idea of the sort-merge algorithm is to first sort the relations by the join attribute, so that interleaved linear scans will encounter these sets at the same time.
In practice, the most expensive part of performing a sort-merge join is arranging for both inputs to the algorithm to be presented in sorted order. This can be achieved via an explicit sort operation (often an external sort), or by taking advantage of a pre-existing ordering in one or both of the join relations.[1] The latter condition, called interesting order, can occur because an input to the join might be produced by an index scan of a tree-based index, another merge join, or some other plan operator that happens to produce output sorted on an appropriate key. Interesting orders need not be serendipitous: the optimizer may seek out this possibility and choose a plan that is suboptimal for a specific preceding operation if it yields an interesting order that one or more downstream nodes can exploit.
Complexity
[edit]Let and be relations where . fits in pages memory and fits in pages memory. In the worst case, a sort-merge join will run in I/O operations. In the case that and are not ordered the worst case time cost will contain additional terms of sorting time: , which equals (as linearithmic terms outweigh the linear terms, see Big O notation – Orders of common functions).
Pseudocode
[edit]For simplicity, the algorithm is described in the case of an inner join of two relations left and right. Generalization to other join types is straightforward. The output of the algorithm will contain only rows contained in the left and right relation and duplicates form a Cartesian product.
function Sort-Merge Join(left: Relation, right: Relation, comparator: Comparator) {
result = new Relation()
// Ensure that at least one element is present
if (!left.hasNext() || !right.hasNext()) {
return result
}
// Sort left and right relation with comparator
left.sort(comparator)
right.sort(comparator)
// Start Merge Join algorithm
leftRow = left.next()
rightRow = right.next()
outerForeverLoop:
while (true) {
while (comparator.compare(leftRow, rightRow) != 0) {
if (comparator.compare(leftRow, rightRow) < 0) {
// Left row is less than right row
if (left.hasNext()) {
// Advance to next left row
leftRow = left.next()
} else {
break outerForeverLoop
}
} else {
// Left row is greater than right row
if (right.hasNext()) {
// Advance to next right row
rightRow = right.next()
} else {
break outerForeverLoop
}
}
}
// Mark position of left row and keep copy of current left row
left.mark()
markedLeftRow = leftRow
while (true) {
while (comparator.compare(leftRow, rightRow) == 0) {
// Left row and right row are equal
// Add rows to result
result = add(leftRow, rightRow)
// Advance to next left row
leftRow = left.next()
// Check if left row exists
if (!leftRow) {
// Continue with inner forever loop
break
}
}
if (right.hasNext()) {
// Advance to next right row
rightRow = right.next()
} else {
break outerForeverLoop
}
if (comparator.compare(markedLeftRow, rightRow) == 0) {
// Restore left to stored mark
left.restoreMark()
leftRow = markedLeftRow
} else {
// Check if left row exists
if (!leftRow) {
break outerForeverLoop
} else {
// Continue with outer forever loop
break
}
}
}
}
return result
}
Since the comparison logic is not the central aspect of this algorithm, it is hidden behind a generic comparator and can also consist of several comparison criteria (e.g. multiple columns). The compare function should return if a row is less(-1), equal(0) or bigger(1) than another row:
function compare(leftRow: RelationRow, rightRow: RelationRow): number {
// Return -1 if leftRow is less than rightRow
// Return 0 if leftRow is equal to rightRow
// Return 1 if leftRow is greater than rightRow
}
Note that a relation in terms of this pseudocode supports some basic operations:
interface Relation {
// Returns true if relation has a next row (otherwise false)
hasNext(): boolean
// Returns the next row of the relation (if any)
next(): RelationRow
// Sorts the relation with the given comparator
sort(comparator: Comparator): void
// Marks the current row index
mark(): void
// Restores the current row index to the marked row index
restoreMark(): void
}
Simple C# implementation
[edit]Note that this implementation assumes the join attributes are unique, i.e., there is no need to output multiple tuples for a given value of the key.
public class MergeJoin
{
// Assume that left and right are already sorted
public static Relation Merge(Relation left, Relation right)
{
Relation output = new Relation();
while (!left.IsPastEnd && !right.IsPastEnd)
{
if (left.Key == right.Key)
{
output.Add(left.Key);
left.Advance();
right.Advance();
}
else if (left.Key < right.Key)
left.Advance();
else // if (left.Key > right.Key)
right.Advance();
}
return output;
}
}
public class Relation
{
private List<int> list;
public const int ENDPOS = -1;
public int position = 0;
public int Position => position;
public int Key => list[position];
public bool IsPastEnd => position == ENDPOS;
public bool Advance()
{
if (position == list.Count - 1 || position == ENDPOS)
{
position = ENDPOS;
return false;
}
position++;
return true;
}
public void Add(int key)
{
list.Add(key);
}
public void Print()
{
foreach (int key in list)
Console.WriteLine(key);
}
public Relation(List<int> list)
{
this.list = list;
}
public Relation()
{
this.list = new List<int>();
}
}
See also
[edit]References
[edit]- ^ "Sort-Merge Joins". www.dcs.ed.ac.uk. Retrieved 2022-11-02.