Skip to content

docs(external): fix memory enrichment table highlight wording #23216

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pront merged 2 commits into from
Jun 16, 2025
Merged

docs(external): fix memory enrichment table highlight wording #23216

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e6d5c3b
docs(external): fix memory enrichment table highlight wording
pront Jun 16, 2025
45ab9c4
improve wording
pront Jun 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 4 additions & 13 deletions website/content/en/highlights/2025-02-24-memory_enrichment_table.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,21 +102,12 @@ calculation the first time it encounters a key. Subsequently, every time the sam
the processing step will be skipped since the pre-computed value is present in the table. The values
can expire; in that case, the computation step will be repeated.

## Use as a sink
## Populate with other components

This new table type can also be used as a sink to feed it data, which can then be queried
like any other enrichment table. For example, here is how to introduce this new component as a sink
if you have another source that can populate the cache:
This new table type also accepts `inputs`, meaning that sources and/or transforms can populate it with data, similar to how a sink operates.
The data can then be queried like any other enrichment table. The configuration above demonstrates this behavior.

```yaml
memory_table_sink:
inputs: [ "another_source_or_transform" ]
type: memory_enrichment_table
ttl: 60
flush_interval: 5
```

We plan to make this component even more flexible in the future. For example, it can also act as a
> We plan to make this component even more flexible in the future. For example, it can also act as a
source. This exercise raises some important questions on component flexibility. The end goal is
treating components as nodes in a graph, unlocking even greater possibilities, such as chaining
sinks.
Loading