Troubleshooting content graph merge and rebase operations
Content repositories and content graphs in the Twinfox Platform offer merge and rebase functionality similar to such abilities with software code repositories, but adapted for content graph processing.
Rebase changes from another content graph
The rebase operation is the conceptually simpler operation. It will replay all changes since the last common historical version of the content graphs (also known as branches). The changes pulled from the other branch get replayed onto the current content graph history.
Both model and instance information will be replayed, in contrast with the merge operation that only operates on content/instance information.
Merge content from another content graph
Content graphs in the Twinfox Platform can be compared with other content graphs or immutable layers in the platform, as long as there is a common ancestor in the version history. The changes get analyzed by the engine and if a merge is possible with the current content graph model, the merge will be applied.
A challenge with merging is to manage model changes between versions of the branch and such model changes need to be carefully managed. If merge operations are important for the use case, and model changes are inevitable, it can be worthwhile to explore model migrations and the diff operations to manually process merges. Such manual merge is currently not supported by the user interface of the platform and only offered using the APIs.
Related Articles
How can I learn more about DFRNT
Learning about DFRNT is closely connected to leveraging the open source TerminusDB data product engine, for which DFRNT is a UI and hosting provider. DFRNT is a user interface and hosting provider for the open source TerminusDB data product ...
Overview of DFRNT data modelling
The data model in DFRNT data products follows the TerminusDB graph metamodel 1:1, and enables easy data modelling and advanced visualisation The data modelling capabilities of DFRNT.com involves five categories of data structures: Records, ...
Render and browse records as Markdown documents, together with inbound and outbound links
Data in DFRNT can be browsed like a wiki, complete with inbound and outbound links so that data can be navigated freely and for exploration with Markdown for rich text. Document contents can be viewed by opening a record through the canvas, or by ...
Data product translations as branches
The recommended way to maintain data product translations is to use the branching method, where each branch corresponds to a language, and use a common schema where each label is translated as part of the schema documentation. Data product ...
Reverse clone from localhost instance
DFRNT model-based data products are supported both in cloud and on your local computer by running a local TerminusDB instance. The cloud instances can't connect to your localhost computer, and thus cloning local data products to cloud needs to be ...