Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 07ea54c) | patch
Parse OrderBy 51/90751/2
authorstatta <statta@research.att.com>
Mon, 1 Jul 2019 19:09:39 +0000 (15:09 -0400)
committerstatta <statta@research.att.com>
Mon, 1 Jul 2019 19:14:25 +0000 (15:14 -0400)
commite5193d27f0f6d0ded1c59360f89e0543ee7f10aa
tree2b698413f0f417de4b4f8d4e82a8c3071d1d18cbtree | snapshot
parent07ea54cfc9341cfc5cc64526e1d357981e6841edcommit | diff
Parse OrderBy

Issue-ID: MUSIC-423

Also add debugging logic

Change-Id: I665675a5da1617f53163e045990ea9f804a8b3ec
Signed-off-by: statta <statta@research.att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/MdbcConnection.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/ownership/Dag.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/ownership/OwnershipAndCheckpoint.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/query/QueryProcessor.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.