liaochuntao created DERBY-7073:
----------------------------------
Summary: Can we override the underlying storage to implement a
distributed Derby using Derby's subsubprotocol mechanism
Key: DERBY-7073
URL: https://issues.apache.org/jira/browse/DERBY-7073
Project: Derby
Issue Type: Task
Reporter: liaochuntao
/**
* derby.subSubProtocol.xxx
*<p>
*
* A new subsubprotocol can be defined by specifying the class that handles
storage for the
* subsubprotocol by implementing the
* org.apache.derby.io.StorageFactory StorageFactory or
* org.apache.derby.io.WritableStorageFactory WritableStorageFactory interface.
This
* is done using a property named db2j.subsubprotocol.<i>xxx</i> where
<i>xxx</i> is the subsubprotocol name.
* Subsubprotocol names are case sensitive and must be at least 3 characters in
length.
*<p>
*
* For instance:
*<br>
* derby.subSubProtocol.mem=com.mycompany.MemStore
*<br>
* defines the "mem" subsubprotocol with class com.mycompany.MemStore as its
StorageFactory implementation.
* A database implemented using this subsubprotocol can be opened with the URL
"jdbc:derby:mem:myDatabase".
*<p>
*
* Subsubprotocols "directory", "classpath", "jar", "http", and "https" are
built in and may not be overridden.
*/
Can we take advantage of this capability to implement a distributed
contribution storage, with Derby acting as the computing layer and multiple
Derby nodes contributing a storage layer, and realize Ploar DB similar to ali
cloud, namely a distributed Derby
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
