Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: a40ee88) | patch
Include primary key in insert query 16/83416/1
authorTschaen, Brendan <ctschaen@att.com>
Tue, 26 Mar 2019 21:28:39 +0000 (17:28 -0400)
committerTschaen, Brendan <ctschaen@att.com>
Tue, 26 Mar 2019 21:28:39 +0000 (17:28 -0400)
commit999f808ea68eeeacf7af36f44a0fea8f9fe6ed88
tree572176cbcea6968ab7d5f1368d8155ea4fbf05bbtree | snapshot
parenta40ee886c28bc28db1794792f1fb312b723d48fbcommit | diff
Include primary key in insert query

Allows replays to easily modify an insert into an update if needed

Change-Id: Ibd0c077240a23aeff3d82ec171c1cecb3274e211
Issue-ID: MUSIC-371
Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
mdbc-server/src/main/java/org/onap/music/mdbc/examples/MdbcTestClient.java diff | blob | history
mdbc-server/src/main/java/org/onap/music/mdbc/mixins/MySQLMixin.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.