Code Review / music / mdbc.git / commitdiff
? search:
summary | shortlog | log | commit | commitdiff | review | tree
raw | patch | inline | side by side (parent: a98c068)
Update MUSIC version 00/92300/2
authorTschaen, Brendan <ctschaen@att.com>
Tue, 30 Jul 2019 17:11:20 +0000 (13:11 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Tue, 30 Jul 2019 17:47:03 +0000 (13:47 -0400)
Issue-ID: MUSIC-466
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
Change-Id: I702b03282f12b02cc59942828a153e1f13cfc620

pom.xml patch | blob | history

diff --git a/pom.xml b/pom.xml
index 14f132c..91e1722 100755 (executable)
--- a/pom.xml
+++ b/pom.xml
@@ -229,8 +229,8 @@
         </dependency>
         <dependency>
             <groupId>org.onap.music</groupId>
-            <artifactId>dev-MUSIC-cassandra</artifactId>
-            <version>3.2.1</version>
+            <artifactId>MUSIC</artifactId>
+            <version>3.2.34-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.