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

Search Engines

As of eZ Publish Platform 5= .4.5 and higher, semantic configuration of search engine connec= tion is implemented in search engine's bundle extension, in order to allow = for search engine's specific settings.

For each integrated Search Engine, you can act= ivate the proper Bundles in the kernel, after which the engine will be avai= lable for configuration.

Currently 3 search engines exists :

  1. Legacy&n= bsp;>=3D 5.= 0.0
  2. Solr integration >=3D 5.4.5
  3. Elast= icSearch integrationEXPERIMENTAL
Recommendation

As of eZ Publish Platform 5.4.5 and higher, Solr is the rec= ommended search engine for production use of the API. Currently Elastic Sea= rch is experimental, not professionally supported, and won't be made= stable anytime soon.

Note: Solr Bundle does not support advanced search features= like out-of-the-box facets (making custom facets is possible), sp= ellchecking and so on, for that continue to use ezfind as those features wi= ll most likely not be backported to 5.4 (Bundle and kernel). This = recommendation regards speeding up the API as a lot of API interactions is = using search api, which gets more stable performance when running on Solr.<= /p>

------=_Part_3589_1536121987.1485853780933--