Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 65b45ca) | patch
Enhance Clob,Blob support 64/89064/1
authorstatta <statta@research.att.com>
Fri, 31 May 2019 16:28:00 +0000 (12:28 -0400)
committerstatta <statta@research.att.com>
Fri, 31 May 2019 16:28:00 +0000 (12:28 -0400)
commit1f36e4303bf76b752eed9ebb8c79a80c31139037
tree4ca30eb5f32459460cbc098396a32d5ec1925452tree | snapshot
parent65b45cafb4dff93bef52e91f2ab3f2a772e4472ecommit | diff
Enhance Clob,Blob support

Issue-ID: MUSIC-388
Change-Id: Ib02df8239e5d7572470fa696697685bdc582cdbb
Signed-off-by: statta <statta@research.att.com>
mdbc-server/src/main/java/org/apache/calcite/avatica/AvaticaSite.java diff | blob | history
mdbc-server/src/main/java/org/apache/calcite/avatica/util/AbstractCursor.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.