Repository navigation
Add EnrichUsingEntityQuery to support business key based enrichment - #4137
Merged
Conversation
Introduce EnrichUsingEntityQuery as a new enrichment mechanism that allows projections to resolve referenced documents using arbitrary business keys instead of document ids. This enables more flexible enrichment scenarios, supports efficient caching of resolved entities, and makes it possible to safely enrich slices without coupling events to storage identifiers.
This was referenced Feb 17, 2026
This was referenced Mar 2, 2026
This was referenced Mar 16, 2026
This was referenced Mar 30, 2026
This was referenced May 11, 2026
This was referenced May 14, 2026
This was referenced May 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduce EnrichUsingEntityQuery as a new enrichment mechanism that allows projections to resolve referenced documents using arbitrary business keys instead of document ids. This enables more flexible enrichment scenarios, supports efficient caching of resolved entities, and makes it possible to safely enrich slices without coupling events to storage identifiers.
Depends on: JasperFx/jasperfx#156