Remove details on the Spring Data for Apache Geode examples from README.
See #654
This commit is contained in:
21
README.adoc
21
README.adoc
@@ -20,27 +20,6 @@ We have separate folders for the samples of individual modules:
|
||||
|
||||
Local Elasticsearch instance must be running to run the tests.
|
||||
|
||||
== Spring Data for Apache Geode
|
||||
|
||||
* `events` - In this example the test will make use of event handlers and async event
|
||||
queue to handle events.
|
||||
* `expiration-eviction` - In these examples the server is configured to delete entries
|
||||
after a certain idle period or after a Time-To-Live period (expiration0 or remove data
|
||||
from memory when certain thresholds are reached (eviction).
|
||||
* `function-invocation` - In this example the server will have 3 functions registered. The
|
||||
client will invoke each of the functions.
|
||||
* `queries` - In this example a client will query the data in various ways using OQl,
|
||||
continuous queries, and Apache Lucene indexes.
|
||||
* `security` - In this example the servers and clients are set up with security (
|
||||
username/password) authentication using Geode Security and Apache Shiro.
|
||||
* `storage` - In this example the server is configured to store data off of hte JVM heap
|
||||
using the `@EnableOffHeap` annotation and to compress region data using
|
||||
SnappyCompressor`.
|
||||
* `transactions` - In this example the client will perform operations within a
|
||||
transaction. First, it will do a successful transaction where entries are saved to the
|
||||
server, and then a failed transaction where all changes are reverted.
|
||||
* `wan` - In these example two servers are deployed. One server populates itself with data, and the other server gets populated with that data via WAN replication.
|
||||
|
||||
== Spring Data JDBC
|
||||
|
||||
* `basic` - Basic usage of Spring Data JDBC.
|
||||
|
||||
Reference in New Issue
Block a user