Add support for In Memory JDBC cache #17
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There are some use cases where we know we have enough memory
and we want to be as fast as possible so we just want to hold
in memory a ResultSet related to a given Statement.
This commit implements a new type of cache using memory
instead of hard disk files.
It uses a naive implementation with ByteArrayStreams which is not recommended for production.
```java
// Initialize the cache driver
Class.forName("com.qwazr.jdbc.cache.Driver");
// Provide the URL and the Class name of the backend driver
Properties info = new Properties();
info.setProperty("cache.driver.url", "jdbc:derby:memory:myDB;create=true");
info.setProperty("cache.driver.class", "org.apache.derby.jdbc.EmbeddedDriver");
// Get your JDBC connection
Connection cnx = DriverManager.getConnection("jdbc:cache:mem:my-memory-cache", info);
```
The syntax of the URL can be:
* *jdbc:cache:file:{path-to-the-cache-directory}* for on disk cache
* *jdbc:cache:mem:{name-of-the-cache}* for in memory cache
|
David, thanks for that great patch. Which improvement would make it a production ready feature? I also had in mind using mmap to have both benefits, memory and persistence. |
dadoonet
added a commit
to dadoonet/jdbc-cache-driver
that referenced
this pull request
Oct 19, 2017
No need to keep a stream of bytes in memory as at the end we need to read it and convert it to an input stream. Related to qwazr#17.
emmanuel-keller
pushed a commit
that referenced
this pull request
Oct 20, 2017
No need to keep a stream of bytes in memory as at the end we need to read it and convert it to an input stream. Related to #17.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are some use cases where we know we have enough memory and we want to be as fast as possible so we just want to hold in memory a ResultSet related to a given Statement.
This commit implements a new type of cache using memory instead of hard disk files.
It uses a naive implementation with ByteArrayStreams which is not recommended for production.
The syntax of the URL can be: