ATLAS-4889: Incremental export : When an entity has tag propagated an… #399
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
pareshddevalia
suggested changes
Jul 14, 2025
repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java
Outdated
Show resolved
Hide resolved
repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java
Outdated
Show resolved
Hide resolved
repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java
Outdated
Show resolved
Hide resolved
repository/src/main/java/org/apache/atlas/repository/impexp/ExportService.java
Outdated
Show resolved
Hide resolved
…d is exported , the tag is not propagated to it in the export.
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.
…d is exported , the tag is not propagated to it in the export.
What changes were proposed in this pull request?
STEPS TO REPRODUCE:
Create table1
Create lineage CTAS tables of depth 10 ( t1 -> t2 -> t3 ..... t10)
Associate tag tag1 to table1
Export table table10
Import the zip
CURRENT BEHAVIOUR:
table10 doesn't have the tag associated to the it since the "entityGUID" is of table1's and table1 is not exported
EXPECTED BEHAVIOUR:
table10 should have tag1 exported
Proposed solution:
While exported we will fetch lineage from table10 backtracking till table1 or corresponding parent
On import user will have child as well as entire lineage till parent which will not break current logic
-Tag is propagated to child on import only if parent is present
How was this patch tested?
Combinations of Tag propagation,Blocktagpropagation feature
Tested with below lineage where multiple incoming edges are present