Code Review / music / mdbc.git / commitdiff
? search:
summary | shortlog | log | commit | commitdiff | review | tree
raw | patch | inline | side by side (parent: 84c322b)
Dependency missing in nexus 75/94375/2
authorsubhash kumar singh <subhash.kumar.singh@huawei.com>
Tue, 27 Aug 2019 19:44:00 +0000 (01:14 +0530)
committersubhash kumar singh <subhash.kumar.singh@huawei.com>
Wed, 28 Aug 2019 09:36:22 +0000 (15:06 +0530)
Dependency missing in nexus.

Change-Id: I91a1db6a839bdd30e788b3cb68aacdd301083a4c
Issue-ID: MUSIC-466
Signed-off-by: subhash kumar singh <subhash.kumar.singh@huawei.com>
pom.xml patch | blob | history

diff --git a/pom.xml b/pom.xml
index 91e1722..5256435 100755 (executable)
--- a/pom.xml
+++ b/pom.xml
@@ -230,7 +230,7 @@
         <dependency>
             <groupId>org.onap.music</groupId>
             <artifactId>MUSIC</artifactId>
-            <version>3.2.34-SNAPSHOT</version>
+            <version>3.2.35-SNAPSHOT</version>
             <exclusions>
                 <exclusion>
                     <groupId>io.netty</groupId>
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.