# US 2023/0156066 A1 · Joining and dimensional annotation in a streaming pipeline

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2023/0156066 A1
- Document ID: US20230156066A1
- Status: Published application
- Kind: A1
- Application number: 18/155,026
- Filed: 2023-01-16
- Published: 2023-05-18
- Earliest claimed: 2020-05-22
- Assignees: Yahoo Assets LLC
- Applicants: Yahoo Assets LLC
- Inventors: Michael PIPPIN; David WILLCOX; Allie K. WATFA; George ALEKSANDROVICH
- Web page: https://patentgrep.com/patent/US20230156066A1

## CPC

- H04L 51/18: Commands or executable codes
- G06F 7/32: Merging, i.e. combining data contained in ordered sequence on at least two record carriers to produce a single carrier or set of carriers having all the original data in the ordered sequence {merging methods in general}(G06F7/36 takes precedence)
- G06F 16/24568: {Data stream processing; Continuous queries}
- H04L 45/028: Dynamic adaptation of the update intervals, e.g. event-triggered updates
- H04L 65/762: {at the source (reformatting of additional data in video distribution servers H04N21/2355)}
- H04L 65/765: {intermediate}
- H04L 65/80: Responding to QoS
- H04L 67/1046: {Joining mechanisms}
- H04L 67/2871: Implementation details of single intermediate entities
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Disclosed are embodiments for providing batch performance using a stream processor. In one embodiment, a method is disclosed comprising receiving, at a stream processor, an event, the stream processor including a plurality of processing stages; generating, by the stream processor, an augmented event based on the event, the augmented event including at least one additional field not appearing in the event, the additional field generated by an operation selected from the group consisting of a join or dimensional annotation operation; and emitting, by the stream processor, the augmented event to downstream consumer.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method comprising:
receiving, at a stream processor, an event, the stream processor including a plurality of processing stages;
querying, by the stream processor, a join table to identify a secondary event associated with the event;
emitting, by the stream processor, the event to downstream consumer if the secondary event is not present in the join table; and
emitting, by the stream processor, an augmented event using the event and the secondary event when the secondary event is present in the join table.

### Claim 22 (depends on 21)

The method of claim 21, further comprising querying the join table to determine if the event is in the join table prior to querying the join table to identify the secondary event and writing the event to the join table if the event is not in the join table.

### Claim 23 (depends on 22)

The method of claim 22, wherein querying the join table to determine if the event is in the join table comprises extracting a join key from the event and querying the join table using the join key.

### Claim 24 (depends on 22)

The method of claim 22, wherein querying the join table to identify the secondary event and querying the join table to determine if the event is in the join table comprise a single query.

### Claim 25 (depends on 21)

The method of claim 21, further comprising labeling the secondary event if the secondary event is present in the join table.

### Claim 26 (depends on 25)

The method of claim 25, wherein labeling the secondary event comprises setting a join status header field of the secondary event in the join table.

### Claim 27 (depends on 21)

The method of claim 21, further comprising augmenting the secondary event if the secondary event is present in the join table to form the augmented event, the augmented event including one or more fields from the event.

### Claim 28

A non-transitory computer-readable storage medium for tangibly storing computer program instructions capable of being executed by a computer processor, the computer program instructions defining steps of:
receiving, at a stream processor, an event, the stream processor including a plurality of processing stages;
querying, by the stream processor, a join table to identify a secondary event associated with the event;
emitting, by the stream processor, the event to downstream consumer if the secondary event is not present in the join table; and
emitting, by the stream processor, an augmented event using the event and the secondary event when the secondary event is present in the join table.

### Claim 29 (depends on 28)

The non-transitory computer-readable storage medium of claim 28, further comprising querying the join table to determine if the event is in the join table prior to querying the join table to identify the secondary event and writing the event to the join table if the event is not in the join table.

### Claim 30 (depends on 29)

The non-transitory computer-readable storage medium of claim 29, wherein querying the join table to determine if the event is in the join table comprises extracting a join key from the event and querying the join table using the join key.

### Claim 31 (depends on 29)

The non-transitory computer-readable storage medium of claim 29, wherein querying the join table to identify the secondary event and querying the join table to determine if the event is in the join table comprise a single query.

### Claim 32 (depends on 28)

The non-transitory computer-readable storage medium of claim 28, further comprising labeling the secondary event if the secondary event is present in the join table.

### Claim 33 (depends on 32)

The non-transitory computer-readable storage medium of claim 32, wherein labeling the secondary event comprises setting a join status header field of the secondary event in the join table.

### Claim 34 (depends on 28)

The non-transitory computer-readable storage medium of claim 28, further comprising augmenting the secondary event if the secondary event is present in the join table to form the augmented event, the augmented event including one or more fields from the event.

### Claim 35

A device comprising:
a stream processor; and
a storage medium for tangibly storing thereon program logic for execution by the stream processor, the program logic comprising instructions for:
receiving an event, the stream processor including a plurality of processing stages;
querying a join table to identify a secondary event associated with the event;
emitting the event to downstream consumer if the secondary event is not present in the join table; and
emitting an augmented event using the event and the secondary event when the secondary event is present in the join table.

### Claim 36 (depends on 35)

The device of claim 35, the instructions further comprising querying the join table to determine if the event is in the join table prior to querying the join table to identify the secondary event and writing the event to the join table if the event is not in the join table.

### Claim 37 (depends on 36)

The device of claim 36, wherein querying the join table to determine if the event is in the join table comprises extracting a join key from the event and querying the join table using the join key.

### Claim 38 (depends on 36)

The device of claim 36, wherein querying the join table to identify the secondary event and querying the join table to determine if the event is in the join table comprise a single query.

### Claim 39 (depends on 35)

The device of claim 35, the instructions further comprising labeling the secondary event if the secondary event is present in the join table.

### Claim 40 (depends on 35)

The device of claim 35, further comprising augmenting the secondary event if the secondary event is present in the join table to form the augmented event, the augmented event including one or more fields from the event.
