Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: c8b5297) | patch
Update sql parse interface 13/77913/4
authorTschaen, Brendan <ctschaen@att.com>
Tue, 5 Feb 2019 20:12:48 +0000 (15:12 -0500)
committerTschaen, Brendan <ctschaen@att.com>
Thu, 7 Feb 2019 16:03:57 +0000 (11:03 -0500)
commit019a55afae68f555348d60cc197b0d188eaaf4af
tree5974bf9d9035c3d2c7eac37a3db50e8e2a7692detree | snapshot
parentc8b529749f19a1705a4fd0791eb83710c0b53e7dcommit | diff
Update sql parse interface

Created junit tests
Fix files code formatting

Issue-ID: MUSIC-311

Change-Id: I9e11a17482a2567055fdee0da8e206ac92235d5f
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/pom.xml diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/query/QueryProcessor.java diff | blob | history
mdbc-server/src/test/java/org/onap/music/mdbc/query/QueryProcessorTest.java [new file with mode: 0644] blob
pom.xml 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.