-
Notifications
You must be signed in to change notification settings - Fork 22
Open
Description
This will become more prominent. When a separate graph gets updated, how do we make sure it gets updated in a robust fashion?
- Add version/identifier to datase before uploading into virtuoso
- Check version in database and update when changes in a new graph
- Test graph
- On success delete old graph and rename new one
That way uploads are minimal and there is no service disruption. The test is critical.
The current method only uploads graphs when the main pipeline completes a run.
Reactions are currently unavailable