| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2018-11-20 | Merge "TxDigest replay and code restructure" |   Bharath Balasubramanian | 28 | -665/+764 | |
| 2018-11-19 | Query processing with Calcite |   Vikram Potturi | 44 | -0/+282 | |
| Change-Id: Id8ebbc48159810ca782081bb4f63071071c926dd Issue-ID: MUSIC-164 Signed-off-by: Vikram Potturi <vikramaditya.potturi@att.com> | |||||
| 2018-11-16 | TxDigest replay and code restructure |   Tschaen, Brendan | 28 | -665/+764 | |
| Spin off replay daemon in its own object Create musictxdaemon test Fix licensing issue MusicRow Info has database partition object Change-Id: I22117f8e9309fb5d8bc99ec35d4145e655f4e5a2 Issue-ID: MUSIC-166 Signed-off-by: Tschaen, Brendan <ctschaen@att.com> | |||||
| 2018-11-14 | Remove unwanted Trigger creation |   st782s | 5 | -3/+12 | |
| Issue-ID: MUSIC-186 Change-Id: I81863e57912d72360676e7d38ed414da4c9e8b17 Signed-off-by: st782s <statta@research.att.com> | |||||
| 2018-11-06 | Self contain the unit tests | Tschaen, Brendan | 1 | -3/+1 | |
| Change-Id: Ib160116a075a1634f9d9cb6bf2527a010fc0e573 Issue-ID: MUSIC-177 Signed-off-by: Tschaen, Brendan <ctschaen@att.com> | |||||
| 2018-11-05 | Modularized mdbc build |   Rob Daugherty | 68 | -0/+13115 | |
| The mdbc pom should inherit from oparent. The top-level pom should not build the jar directly. It should be a parent pom for mdbc submodules. The first submodule will be called mdbc-server. Note: the "mdbc" jar will now be called "mdbc-server". Change-Id: I4456e659b7494641e5b3cefd540eb62a149b79a4 Issue-ID: MUSIC-175 Signed-off-by: Rob Daugherty <rd472p@att.com> | |||||
 |
index : music/mdbc | |
| 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. | Grokmirror user |
| aboutsummaryrefslogtreecommitdiffstats |