Remove obsolete method hasKeyspace() from KeyValueAdapter. Transition from List to Iterable for find methods in KeyValueTemplate. We now offer a plug able KeySpace resolution by providing a KeySpaceResolver via the KeyValueMappingContext. By default an AnnotationBasedKeySpaceResolver will be used to examine the type for @KeySpace. In case of non explicit keySpace we fall back to using the class' fully-qualified name as the default key space. Key space resolution is now fixed on resolving @KeySpace on a given PersistentEntity. In case no annotation key space can be found we by default fall back to a class name based key space. It is possible to configure the fallback via the MappingContext. Refactored names & visibility of types required for tests. Removed shortcut for returning results not having an explicit key space, since we now can no longer rely on the type name strategy dividing non explicit types into separate key spaces. Original pull request: #11.
Spring Data Key Value
The primary goal of the Spring Data project is to make it easier to build Spring-powered applications that use data access technologies. This module provides infrastructure components to build repository abstractions for stores dealing with Key/Value pairs and ships with a default java.util.Map based implementation.
Features
- Infrastructure for building repositories on top of key/value implementations.
- Dynamic SpEL query generation from query method names.
- Possibility to integrate custom repository code.
Quick Start
Download the jar though Maven:
<dependency>
<groupId>org.springframework.data</groupId>
<artifactId>spring-data-keyvalue</artifactId>
<version>0.1.0.BUILD-SNAPSHOT</version>
</dependency>
For snapshot versions, make sure you include the spring snapshots repository:
<repositories>
<repository>
<id>spring-libs-snapshot</id>
<url>http://repo.spring.io/libs-snapshot</url>
</repository>
</repositories>
The ConcurrentHashMap based default configuration looks like this:
@Configuration
@EnableMapRepositories("com.acme.repositories")
class AppConfig {
}
Note it is possible to change the used java.util.Map implementation via @EnableMapRepositories(mapType=... .class).
Create the domain type and use @KeySpace to explicitly group values into one region. By default the types class name is used.
@KeySpace("user")
class User {
@Id String uuid;
String firstname;
}
Create a repository interface in com.acme.repositories:
public interface UserRepository extends CrudRepository<User, String> {
List<String> findByLastname(String lastname);
}
QueryDSL
To use Querydsl with Spring Data KeyValue repositories com.mysema.querydsl:querydsl-collections:3.6.0 (or better) needs to be present.
Just add QueryDslPredicateExecutor to the repository definition and use com.mysema.query.types.Predicate to define the query.
Tips
To have the maximum performance we encourage you to use the latest Spring 4.1.x or better release with compiled SpEL expressions enabled.
-Dspring.expression.compiler.mode=IMMEDIATE
Contributing to Spring Data Key Value##
Here are some ways for you to get involved in the community:
- Get involved with the Spring community by helping out on stackoverflow by responding to questions and joining the debate.
- Create JIRA tickets for bugs and new features and comment and vote on the ones that you are interested in.
- Github is for social coding: if you want to write code, we encourage contributions through pull requests from forks of this repository. If you want to contribute code this way, please reference a JIRA ticket as well covering the specific issue you are addressing.
- Watch for upcoming articles on Spring by subscribing to spring.io.
Before we accept a non-trivial patch or pull request we will need you to sign the contributor's agreement. Signing the contributor's agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests.