Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: a05dc5d) | patch
Remove duplicate table creation 67/95967/2
authorsubhash.kumar.singh <subhash.kumar.singh@huawei.com>
Thu, 19 Sep 2019 07:05:39 +0000 (12:35 +0530)
committersubhash.kumar.singh <subhash.kumar.singh@huawei.com>
Thu, 19 Sep 2019 08:50:42 +0000 (14:20 +0530)
commit524904eaedd84201ae008c9098aebcaa69181d14
treedcc5e986956013349512f02ea02cbc11978c11a4tree | snapshot
parenta05dc5ddab778a0305402c8d1ecb6297e9fbd9aacommit | diff
Remove duplicate table creation

Remove code to create table as it is already done by the MusicMixin
constructor.

Added java8 syntax enhancement.

Change-Id: Ic04987d701e969466f40fbe255576b85206032f9
Signed-off-by: subhash.kumar.singh <subhash.kumar.singh@huawei.com>
Issue-ID: MUSIC-412
mdbc-server/src/test/java/org/onap/music/mdbc/MdbcTestUtils.java diff | blob | history
mdbc-server/src/test/java/org/onap/music/mdbc/mixins/MusicMixinTest.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.