zquintana/sun-search-bundle

Symfony Solr integration bundle

SunSearchBundle (SolrBundle fork)

Introduction

This Bundle provides a simple API to index and query a Solr Index., _(*1)

Installation

Installation is a quick (I promise!) 3 step process:, _(*2)

1. Download SunSearchBundle
2. Enable the Bundle
3. Configure the SunSearchBundle

Step 1: Download ZQSunSearchBundle

This bundle is available on Packagist. You can install it using Composer:, _(*3)

$ composer require zquintana/sun-search-bundle

Step 2: Enable the bundle

Next, enable the bundle in the kernel:, _(*4)

``` php <?php // app/AppKernel.php, <sub>(*5)</sub>

public function registerBundles() { $bundles = array( // ... new ZQ\SunSearchBundle\ZQSunSearchBundle(), ); }, <sub>(*6)</sub>

### Step 3: Configure the ZQSunSearchBundle

Finally, configure the bundle:

``` yaml
# app/config/config.yml
sun_search:
    connections:
        default:
            host: host
            port: 8983
            path: /solr/core0
            timeout: 5

    cores:
        corename:
            config_set: ~
            connection: ~

Step 4: Configure your entities

To make an entity indexed, you must add some annotations to your entity. Basic configuration requires two annotations: @Sun\Document(), @Sun\Id(). To index data add @Sun\Field() to your properties., <sub>(*7)</sub>

// ....
use ZQ\SunSearchBundle\Doctrine\Annotation as Sun;

/**
* @Sun\Document()
* @ORM\Table()
*/
class Post
{
    /**
     * @Sun\Id
     *
     * @ORM\Column(name="id", type="integer")
     * @ORM\Id
     * @ORM\GeneratedValue(strategy="AUTO")
     */
    private $id;

    /**
     * @Sun\Field(type="string")
     *
     * @ORM\Column(name="title", type="string", length=255)
     */
    private $title = '';

    /**
     * @Sun\Field(type="string")
     *
     * @ORM\Column(name="text", type="text")
     */
    private $text = '';

   /**
    * @Sun\Field(type="date", getter="format('Y-m-d\TH:i:s.z\Z')")
    *
    * @ORM\Column(name="created_at", type="datetime")
    */
    private $created_at = null;
}

Annotation reference

@Sun\Document annotation

This annotation denotes that an entity should be indexed as a document. It has several optional properties:, <sub>(*8)</sub>

• repository
• index
• indexHandler

Setting custom repository class with repository option

If you specify your own repository, the repository must extend the ZQ\SunSearchBundle\Repository\Repository class., <sub>(*9)</sub>

/**
 * @Sun\Document(repository="My/Custom/Repository")
 */
class SomeEntity
{
    // ...
}

index property

It is possible to specify a core the document will be indexed in:, <sub>(*10)</sub>

/**
 * @Sun\Document(index="core0")
 */
class SomeEntity
{
    // ...
}

indexHandler property

By default, all documents will be indexed in the core core0. If your entities/documents have different languages, then you can setup a callback method, which should return the core the entity will be indexed in., <sub>(*11)</sub>

/**
 * @Sun\Document(indexHandler="indexHandler")
 */
class SomeEntity
{
    public function indexHandler()
    {
        if ($this->language == 'en') {
            return 'core0';
        }
    }
}

Each core must be set up in config.yml under endpoints. If you leave the index or indexHandler property empty, then the default core will be used (first one in the endpoints list). To index a document in all cores, use * as index value., <sub>(*12)</sub>

@Sun\Id annotation

This annotation is required to index an entity. The annotation has no properties. You should add this annotation to the field that will be used as the primary identifier for the entity/document., <sub>(*13)</sub>

class Post
{
    /**
     * @Sun\Id
     *
     * @ORM\Column(name="id", type="integer")
     * @ORM\Id
     * @ORM\GeneratedValue(strategy="AUTO")
     */

    private $id;
}

@Sun\Field annotation

This annotation should be added to properties that should be indexed. You should specify the type option for the annotation., <sub>(*14)</sub>

Supported simple field types

Currently, a basic set of types is implemented:, <sub>(*15)</sub>

• string(s)
• text(s)
• date(s)
• integer(s)
• float(s)
• double(s)
• long(s)
• boolean(s)

Object relations

Indexing relations works in simplified way. Related entities will not be indexed as a new document, but only as a searchable value. Related entities do not need a @Sun\Document annotation., <sub>(*16)</sub>

ManyToOne relation

/**
 * @var Category
 *
 * @Sun\Field(type="string", getter="getTitle")
 *
 * @ORM\ManyToOne(targetEntity="Acme\DemoBundle\Entity\Category", inversedBy="posts", cascade={"persist"})
 * @ORM\JoinColumn(name="category_id", referencedColumnName="id")
 */
private $category;

Related entity:, <sub>(*17)</sub>

class Category
{
    /**
     * @return string
     */
    public function getTitle()
    {
        return $this->title;
    }
}

OneToMany relation

To index a set of objects it is important to use the fieldtype strings., <sub>(*18)</sub>

/**
 * @var Tag[]
 *
 * @Sun\Field(type="strings", getter="getName")
 *
 * @ORM\OneToMany(targetEntity="Acme\DemoBundle\Entity\Tag", mappedBy="post", cascade={"persist"})
 */
private $tags;

Related entity:, <sub>(*19)</sub>

class Tag
{
    /**
     * @return string
     */
    public function getName()
    {
        return $this->name;
    }
}

For more information read the more detailed "How to index relation" guide, <sub>(*20)</sub>

@Sun\SynchronizationFilter(callback="shouldBeIndexed") annotation

In some cases, an entity should not be indexed. For this, you have the SynchronizationFilter annotation to run a filter-callback., <sub>(*21)</sub>

/**
 * // ....
 * @Sun\SynchronizationFilter(callback="shouldBeIndexed")
 */
class SomeEntity
{
    /**
     * @return boolean
    */
    public function shouldBeIndexed()
    {
        // put your logic here
    }
}

The callback property specifies an callable function, which should return a boolean value, specifying whether a concrete entity should be indexed., <sub>(*22)</sub>

Queries

Query a field of a document

Querying the index is done via the sunsearch.client service:, <sub>(*23)</sub>

$query = $this->get('sunsearch.client')->createEntityQuery('AcmeDemoBundle:Post');
$query->addSearchTerm('title', 'my title');
$query->addSearchTerm('collection_field', array('value1', 'value2'));

$result = $query->getResult();

or, <sub>(*24)</sub>

$posts = $this->get('sunsearch.client')->getRepository('AcmeDemoBundle:Post')->findOneBy(array(
    'title' => 'my title',
    'collection_field' => array('value1', 'value2')
));

Query all fields of a document

The previous examples were only querying the title field. You can also query all fields with a string., <sub>(*25)</sub>

$query = $this->get('sunsearch.client')->createEntityQuery('AcmeDemoBundle:Post');
$query->queryAllFields('my title');

$result = $query->getResult();

Define a custom query string

If you need more flexiblity in your queries you can define your own query strings:, <sub>(*26)</sub>

$query = $this->get('sunsearch.client')->createEntityQuery('AcmeDemoBundle:Post');
$query->setCustomQuery('id:post_* AND (author_s:Name1 OR author_s:Name2)');

$result = $query->getResult();

Define Result-Mapping

To narrow the mapping, you can use the addField() method., <sub>(*27)</sub>

$query = $this->get('sunsearch.client')->createEntityQuery('AcmeDemoBundle:Post');
$query->addSearchTerm('title', 'my title');
$query->addField('id');
$query->addField('text');

$result = $query->getResult();

In this case, only the id and text fields will be mapped (addField()), title and created_at` fields will be empty. If nothing was found $result is empty., <sub>(*28)</sub>

By default, the result set contains 10 rows. You can increase this value:, <sub>(*29)</sub>

$query->setRows(1000000);

Configure HydrationModes

HydrationMode tells the bundle how to create an entity from a document., <sub>(*30)</sub>

1. ZQ\SunSearchBundle\Doctrine\Hydration\HydrationModes::HYDRATE_INDEX - use only the data from solr
2. ZQ\SunSearchBundle\Doctrine\Hydration\HydrationModes::HYDRATE_DOCTRINE - merge the data from solr with the entire doctrine-entity

With a custom query:, <sub>(*31)</sub>

$query = $this->get('sunsearch.client')->createEntityQuery('AcmeDemoBundle:Post');
$query->setHydrationMode($mode)

With a custom document-repository you have to set the property $hydrationMode itself:, <sub>(*32)</sub>

public function find($id)
{
    $this->hydrationMode = HydrationModes::HYDRATE_INDEX;

    return parent::find($id);
}

Repositories

Your should define your own repository-class to make your custom queries reuseable. How to configure a repository for a document have a look at the annotation section, <sub>(*33)</sub>

namespace AppBundle\Search;

use ZQ\SunSearchBundle\Repository\Repository;

class ProviderRepository extends Repository
{
    public function findPost($what)
    {
        $query = $this->solr->createEntityQuery('AcmeDemoBundle:Post');
        // some query-magic here

        return $query->getResult();
    }
}

Creating Cores

Creating cores via SunSearch can be done 2 ways. To do so programatically use the Core\Query located in SunSearch to create and execute a request to create the core by name with a config set., <sub>(*34)</sub>

~~~ php use ZQ\SunSearchBundle\Solarium\QueryType\Core\Query;, <sub>(*35)</sub>

/** @var Solarium\Client $solr */ $solr = $this->getContainer()->get('sunsearch.client.adapter'); $query = $solr->createQuery(Query::TYPE); $query->createWithConfigSet($coreName, $configSet); $solr->execute($query, $endpoint); ~~~, <sub>(*36)</sub>

Another ways is outlined below through the use the sunsearch:cores:create command. This command requires that you define the config set name as part of your cores configuration., <sub>(*37)</sub>

Commands

Here's all the commands provided by this bundle:, <sub>(*38)</sub>

• sunsearch:cores:create - creates cores via configuration (only works with config sets defined.)
• sunsearch:index:clear - delete all documents in the index
• sunsearch:index:populate - synchronize the db with the index
• sunsearch:schema:show - shows your configured documents

Extend Solarium

To extend Solarium with your own plugins, create a tagged service:, <sub>(*39)</sub>

<tag name="solarium.client.plugin" plugin-name="yourPluginName"/>

To hook into the Solarium events create a common Symfony event-listener:, <sub>(*40)</sub>

<tag name="kernel.event_listener" event="solarium.core.preExecuteRequest" method="preExecuteRequest" />