Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 1ec3887) | patch
Row re-use fix 73/85473/1
authorTschaen, Brendan <ctschaen@att.com>
Tue, 16 Apr 2019 13:51:58 +0000 (09:51 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Tue, 16 Apr 2019 13:51:58 +0000 (09:51 -0400)
commiteff522e4e38b11432f518d1b43fda01d8d387ca4
treee6a1d44ec07874cb40b40788563ea51b7c6669f6tree | snapshot
parent1ec38875f207407ad8f4dc5b428e5ca47f016d5fcommit | diff
Row re-use fix

This prevents rows from being split properly, will follow up on issue

Change-Id: I6d9ebbf8cf9abd2cac4992be407fb6cb44cb318b
Issue-ID: MUSIC-326
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/DatabasePartition.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MusicMixin.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/ownership/OwnershipAndCheckpoint.java diff | blob | history
The most crucial recipe is a multi-site database cache (mdbc) that enable ONAP components that maintain state in a SQL database to avail the benefits of MUSIC without compromising their need to use transactional SQL DBs. These ONAP components can rely on existing db clustering techniques like MariaDB for transactionality and complex querying within a site. mdbc will intercept each of these read/write calls to the db cluster and mirror this state to other geo-distributed sites through MUSIC either synchronously or asynchronously (configurable at a table-level). For example, components like the ONAP Service Orchestrator that use MariaDB to maintain state can directly use this recipe with no change to their SQL code.