Versioning document changes in Vespa

database-versioning vespa

I would like to allow for versioning of text in Vespa. If a user changes certain fields over time the changes would be tracked and versions could be restored.

I imagine a solution running in parallel to Vespa would be the way to go, with version numbers being stored in the vespa doc as unindexed data.

Any recommendations on a solution to use to do this? Something like http://jsonpatch.com?


Solution 1:

I would just store each version as a separate document by including the version in the document id.

Related

Simplest way to concatenate multi lines of text in java through File Handling
Getting the Redirected URL from the Original URL
Typescript: Type 'string' is not assignable to type '"numeric" | "2-digit"' in Date::toLocaleDateString()
swiftUI Core Data @FetchRequest single object
tiptap - Insert node below / at the end of the current one
Understanding Django GenericForeignKey and GenericRelation
sqlite understanding date datatype [duplicate]
How do I get the position of a result in the list after an order_by?
SQLite Database gives warning automatic index on <table_name>(column) After upgrading Android L
MySql - Is primary key unique by default?
Call a static function into the class React ES6
Differences Between Drivers for ODBC Drivers