anchor.diff:          };
       }
   ====
  +
  +Whenever content is indexed this bean will be consulted providing an opportunity to provide the set additional attributes that 
  +you would like to be indexed.
   
   To customize the query that gets executed when a Store's Searchable method is invoked add a `FilterQueryProvider` bean to your 
   application's configuration:
  
positive.code: }
  ----
  1. Specify the `@EnableFullTextSolrIndexing` annotation in an `@Configuration` class
  2. Spring Content Solr works with any Spring Content Store Module
  3. Ensure a `(SolrJ) SolrClient` `@Bean` is instantiated somewhere within your `@Configuration`
  ====
  
  == Configuring
  
  If required, credentials can be specified using the following configuration properties.
  
  
negative.code: With fulltext-indexing enabled, Store interfaces can be made `Searchable`.  See
  <<content-repositories.search,Searchable Stores>> for more information on how to do this.
  
  == Taking control of the indexing process
  
  When you `@EnableFullTextSolrIndexing` a store event handler is registered that intercepts content being added to a
  Store and sends that content to your Solr instance for full-text indexing.  This is usually all you need.  However,
  sometimes you may need more control over when documents are indexed.  For these cases you can use the `IndexService`
  bean directly in your code to index (or unindex) content as required.
  
  == Indexing additional attributes
  
  By default Spring Content Solr indexes content only.  However, it is common to index additional 
  attributes (from the primary domain model) that can then be used for filtering subsequent full-text queries 
  or for efficiently populating search results (removing the need to perform additional queries against the 
  primary domain model).
  
  Add a bean that implements `AttributeProvider` to your application's configuration:
  
  ====
  [source, java]
  