Spring Data - Apache Solr integration
Latest commit ed93176 Dec 6, 2016 @mp911de mp911de DATASOLR-342 - Register SolrRepositoryFactory in spring.factories.
This is required for the switch in support for multi-store detection.

Related ticket: DATACMNS-952.


Spring Data for Apache Solr Spring Data for Apache Solr

Spring Data for Apache Solr

The primary goal of the Spring Data project is to make it easier to build Spring-powered applications that use new data access technologies such as non-relational databases, map-reduce frameworks, and cloud based data services.

The Spring Data for Apache Solr project provides integration with the Apache Solr search engine

Providing its own extensible MappingSolrConverter as alternative to DocumentObjectBinder Spring Data for Apache Solr handles inheritance as well as usage of custom Types such as Point or DateTime.

Getting Help

If you are new to Spring as well as to Spring Data, look for information about Spring projects.

Quick Start


SolrTemplate is the central support class for solr operations.


A default implementation of SolrRepository, aligning to the generic Repository Interfaces, is provided. Spring can do the Repository implementation for you depending on method names in the interface definition.

The SolrCrudRepository extends PagingAndSortingRepository

   public interface SolrCrudRepository<T, ID extends Serializable> extends SolrRepository<T, ID>, PagingAndSortingRepository<T, ID> {

The SimpleSolrRepository implementation uses MappingSolrConverter. In order support native solrj mapping via DocumentObjectBinder fields have to be annotated with org.apache.solr.client.solrj.beans.Field. org.springframework.data.solr.core.mapping.Indexed can be used as substitute for Field offering additional attributes to be used eg. for index time boosting.

To enable native solrj mapping use SolrJConverter along with SolrTemplate.

public interface SolrProductRepository extends SolrCrudRepository<Product, String> {

  //Derived Query will be "q=popularity:<popularity>&start=<page.number>&rows=<page.size>"
  Page<Product> findByPopularity(Integer popularity, Pageable page);

  //Will execute count prior to determine total number of elements
  //Derived Query will be "q=name:<name>*&start=0&rows=<result of count query for q=name:<name>>"
  List<Product> findByNameStartingWith(String name);

  //Derived Query will be "q=inStock:true&start=<page.number>&rows=<page.size>"
  Page<Product> findByAvailableTrue(Pageable page);

  //Derived Query will be "q=inStock:<inStock>&start=<page.number>&rows=<page.size>"
  Page<Product> findByAvailableUsingAnnotatedQuery(boolean inStock, Pageable page);

  //Will execute count prior to determine total number of elements
  //Derived Query will be "q=inStock:false&start=0&rows=<result of count query for q=inStock:false>&sort=name desc"
  List<Product> findByAvailableFalseOrderByNameDesc();

  //Execute faceted search 
  //Query will be "q=name:<name>&facet=true&facet.field=cat&facet.limit=20&start=<page.number>&rows=<page.size>"
  @Query(value = "name:?0")
  @Facet(fields = { "cat" }, limit=20)
  FacetPage<Product> findByNameAndFacetOnCategory(String name, Pageable page);

  //Boosting criteria
  //Query will be "q=name:<name>^2 OR description:<description>&start=<page.number>&rows=<page.size>"
  Page<Product> findByNameOrDescription(@Boost(2) String name, String description, Pageable page);

  //Highlighting results
  //Query will be "q=name:(<name...>)&hl=true&hl.fl=*"
  HighlightPage<Product> findByNameIn(Collection<String> name, Pageable page);

  //Spatial Search
  //Query will be "q=location:[<bbox.start.latitude>,<bbox.start.longitude> TO <bbox.end.latitude>,<bbox.end.longitude>]"
  Page<Product> findByLocationNear(Box bbox);

  //Spatial Search
  //Query will be "q={!geofilt pt=<location.latitude>,<location.longitude> sfield=location d=<distance.value>}"
  Page<Product> findByLocationWithin(Point location, Distance distance);


Furthermore you may provide a custom implementation for some operations.

public interface SolrProductRepository extends SolrCrudRepository<Product, String>, SolrProductRepositoryCustom {

  @Query(fields = { "id", "name", "popularity" })
  Page<Product> findByPopularity(Integer popularity, Pageable page);

  List<Product> findByAuthorLike(String author);


public interface SolrProductRepositoryCustom {

  Page<Product> findProductsByCustomImplementation(String value, Pageable page)


public class SolrProductRepositoryImpl implements SolrProductRepositoryCustom {

  private SolrOperations solrTemplate;

  public Page<Product> findProductsByCustomImplementation(String value, Pageable page) {
    Query query = new SimpleQuery(new SimpleStringCriteria("name:"+value)).setPageRequest(page);
    return solrTemplate.queryForPage(query, Product.class);

  public void setOperations(SolrOperations operations) {
    this.operations = operations;


Go on and use it as shown below:

@EnableSolrRepositories(basePackages = { "com.acme.sorl" }), multicoreSupport = true)
public class SolrContext {

  private @Resource Environment env;

  public SolrClient solrClient() throws MalformedURLException, IllegalStateException {
    return new HttpSolrClient(env.getRequiredProperty("solr.host"));


public class ProductService {

  private SolrProductRepository repository;

  public ProductService(SolrProductRepository repository) {
    this.repository = repository;

  public void doSomething() {

    Product product = new Product("spring-data-solr");
    product.setAuthor("Christoph Strobl");

    Product singleProduct = repository.findById("spring-data-solr");
    List<Product> productList = repository.findByAuthorLike("Chr");


XML Namespace

You can set up repository scanning via xml configuration, which will happily create your repositories.

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
  xsi:schemaLocation="http://www.springframework.org/schema/data/solr http://www.springframework.org/schema/data/solr/spring-solr.xsd
    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd">

  <solr:repositories base-package="com.acme.repository" multicoreSupport="true" />
  <solr:solr-client id="solrClient" url="http://localhost:8983/solr" />


Automatic Schema Population

Automatic schema population will inspect your domain types whenever the applications context is refreshed and populate new fields to your index based on the properties configuration. This requires solr to run in Schemaless Mode.

Use @Indexed to provide additional details like specific solr types to use.

@EnableSolrRepositories(schemaCreationSupport = true, multicoreSupport = true)
class Config {

  public SolrClient solrClient() {
    return new HttpSolrClient("http://localhost:8983/solr");

class Product {

  @Id String id;
  @Indexed(solrType="text_general") String author;
  @Indexed("cat") List<String> category;

// curl ../solr/collection1/schema/fields -X POST -H 'Content-type:application/json'




Build Snapshot



Contributing to Spring Data

Please refer to CONTRIBUTING

Stay in touch

Follow the project team (@stroblchristoph, @SpringData) on Twitter. Releases are announced via our news feed.