Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 8703bea) | patch
Don't call newLocks.put when lockId isn't set 40/84140/2
authorArthur Martella <arthur.martella.1@att.com>
Wed, 3 Apr 2019 19:58:17 +0000 (15:58 -0400)
committerArthur Martella <arthur.martella.1@att.com>
Wed, 3 Apr 2019 20:00:04 +0000 (16:00 -0400)
commita1c1b4ba47e9c8ef1fa4e7b8a3ea8ab272050bae
tree02890f5cc10174b7439fe9f239c20974df3882c1tree | snapshot
parent8703beababa99e3cf7c66995f28cf254de54616dcommit | diff
Don't call newLocks.put when lockId isn't set

Change-Id: I77f5870265712958979d7832eeb845d51e35cfe3
Issue-ID: MUSIC-374
Signed-off-by: arthur.martella.1@att.com
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.