Message-ID: <2036186093.2982.1485851501253.JavaMail.confluence@ip-10-127-227-164> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2981_788125036.1485851501223" ------=_Part_2981_788125036.1485851501223 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Legacy Search Engine Bundle

Legacy Search Engine Bundle

Legacy Search Engine is the default search= engine, it is SQL based and uses Doctrine's database connection. So its co= nnections are, and should be, defined in the same way as for storage engine= , and no further specific configuration is needed.

Its features and performance are limited, and if you have specific searc= h or performance needs you should rather look towards using Solr.

Configuring repository with t= he legacy search engine

Search can be configured in= dependently from storage, and the following configuration example shows bot= h the default values, and how you configure legacy as the search engine:

ezpublish.yml
=20
ezpublish:
    repositories:
        main:
            storage:
                engine: legacy
                connection: default
            search:
                engine: legacy
                connection: default
=20
------=_Part_2981_788125036.1485851501223--