feat(core)!: add ingestion mode management - #127
Open
RVANDO12 wants to merge 9 commits into
Open
Conversation
Code Coverage OverviewLanguages: Java Java / code-coverage/jacocoThe overall coverage in commit 6afe4a6 in the Show a code coverage summary of the most impacted files.
Updated |
…equires an action field. feat(core): add ingestion mode management feat(core): add ingestion mode management - fix sonar issue feat(core): add ingestion mode management - fix sonar issue feat(core): add ingestion mode management - fix swagger breaking change feat(core): add ingestion mode management - fix swagger and useless code
RVANDO12
force-pushed
the
feat/ingestion/mode-management
branch
from
August 14, 2026 13:49
9e32ce7 to
9bdf2f6
Compare
|
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
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.



PR Description
What this PR Provides
MappingActionenum to support granular ingestion modes (UPDATE_ENTITY,UPDATE_PROPERTIES,UPDATE_RELATIONS,DELETE).UPDATE_PROPERTIES) that strictly preserve existing relationship edges.UPDATE_RELATIONS) that strictly preserve existing scalar properties.DELETE) that gracefully cleans up parent relation references before removing the entity.EntityDynamicMappingconfiguration to accept and validate the required action mode.Fixes
Review
The reviewer must double-check these points:
!after the type/scope to identify the breakingchange in the release note and ensure we will release a major version.
How to test
Ensure you have a valid
EntityTemplatedeployed in back-end, and create an initial baseline Entity with both properties and relations populated.Set up a Webhook Connector targeting this template.
UPDATE_PROPERTIESthat alters a property (e.g., status).UPDATE_RELATIONSthat alters a relationship target array.UPDATE_RELATIONSwith an empty array[]for a specific relation.DELETE.GETrequest should show the property updated while all original relations remain untouched.GETrequest should show the relation updated while all original properties remain untouched.GETrequest should show the relation successfully unlinked (cleared).GETrequest to the entity should return a 404 Not Found, and any parent entities that previously referenced it should no longer contain its ID in their relation arrays.Breaking changes !
Context of the Breaking Change
The API schema for configuring Webhook Connectors has been modified. The
EntityDynamicMappingpayload now requires anactionfield to dictate the mutation logic.Result of the Breaking Change
Existing webhook mapping configurations must be migrated to include
"action": "UPDATE_ENTITY"to retain their current default behavior (Full Merge).