ATLAS-5320: Distributed Notification Processing#671
Open
rkundam wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
To support high-volume metadata ingestion while preserving lineage accuracy and data consistency, https://issues.apache.org/jira/browse/ATLAS-5320 introduced a distributed parallel processing architecture. Rather than relying on a single-threaded sequential pipeline, the system partitions entity workloads deterministically and processes independent entity families concurrently.
How was this patch tested?
Tested with different sets of data in clusters and compared with Serial Processing for the same datasets.
Ex: For below dataset, Serial Processing took around 5hrs and Distributed Parallel processing with 3 metadata and 3 lineage topics it took 1.5hrs.
Tables: 6.5K
Column: 130K
Lineage: 1.7K