Code Review / music / mdbc.git / commitdiff
? search:
summary | shortlog | log | commit | commitdiff | review | tree
raw | patch | inline | side by side (parent: 04ab889)
Update oparent version 69/86769/1
authorJessica Wagantall <jwagantall@linuxfoundation.org>
Thu, 2 May 2019 02:16:05 +0000 (19:16 -0700)
committerJessica Wagantall <jwagantall@linuxfoundation.org>
Thu, 2 May 2019 02:16:05 +0000 (19:16 -0700)
Update oparent version to 2.0.0 which supports
global-jjb maven-stage job.

Change-Id: Ib9f38fbae9e95099856e6dda1d3ace2dc236c747
Issue-ID: CIMAN-234
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
pom.xml patch | blob | history

diff --git a/pom.xml b/pom.xml
index e27fd09..14f132c 100755 (executable)
--- a/pom.xml
+++ b/pom.xml
@@ -35,7 +35,7 @@
     <parent>
         <groupId>org.onap.oparent</groupId>
         <artifactId>oparent</artifactId>
-        <version>1.2.1</version>
+        <version>2.0.0</version>
     </parent>
 
     <properties>
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.