Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • predicate: The predicate to evaluate over each incoming tuple from left and right
  • card: ONE_ONE, ONE_MANY, MANY_ONE, MANY_MANY (same as empty, see below)
  • SweepAreaName: Overwrite the default rule for using sweepAreas (e.g. TIJoinSA is used if the predicate contains other operations than "==", HashJoinSA is used if the predicate only contains "==")

  • elementsizeport0, elementsizeport0 (see below)
  • group_by_port_0, group_by_port_1 (see below)

...

Code Block
SELECT * FROM left, right WHERE auction_id = auction

Element Join
Anchor
elementjoin
elementjoin

Sometimes it is necessary to have an element window before a join, for example, to only use the latest element for each or from one of the two input ports. Unfortunately, an element window has a blocking behavior. Using the element join avoids this blocking behavior by integrating the element window into the join operator itself. Therefore, there is no need to manually add an element window operator before this join.

With the parameters elementsizeport0 and elementsizeport1, the size of the element window can be defined for each input port. Optionally, the counter can be grouped, for example by a certain id, as can be seen in the example below.

Code Block
JOIN({
    elementsizeport1 = 1,
    elementsizeport0 = 1,
    group_by_port_1 = ['id'],
    group_by_port_0 = ['id_center']              
}, left, right)