Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 9693352) | patch
Fix Clob,Blob read and writes 24/88024/1
authorstatta <statta@research.att.com>
Fri, 17 May 2019 18:55:18 +0000 (14:55 -0400)
committerstatta <statta@research.att.com>
Fri, 17 May 2019 18:58:50 +0000 (14:58 -0400)
commited4b4af2de4b02efd3f097323e9a999f905e60e6
tree919a170162967b07443e7cf97b487dc25038cc2ctree | snapshot
parent96933528fdd51e606e48d79941ce43249ffb48b6commit | diff
Fix Clob,Blob read and writes

Issue-ID: MUSIC-388

Change-Id: I3ddd84f097231a21423325b04c34a4a90e4ea0e0
Signed-off-by: statta <statta@research.att.com>
mdbc-server/src/main/java/org/apache/calcite/avatica/AvaticaSite.java [new file with mode: 0644] blob
mdbc-server/src/main/java/org/apache/calcite/avatica/util/AbstractCursor.java [new file with mode: 0644] blob
mdbc-server/src/main/java/org/onap/music/logging/EELFLoggerDelegate.java diff | blob | history
mdbc-server/src/main/resources/logback.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.