JahiaOne 2015 - Search at scale: free Digital Factory from running searches!

© 2002 - 2015 Jahia Solutions Group SA

Search at scaleFree Digital Factory from running searches!

Christophe Laprun / Kevan JahanshahiJahia Solutions Group SA


Current architecture Searching most easily accomplished using

JSP taglib Uses SearchService Delegates to SearchProvider JahiaJCRSearchProvider relies on Lucene

to perform search at the JCR level


Limitations Search contends for JCR access with

"regular" operations Difficult to scale Difficult to support some use cases using

"pure" Lucene


Idea: externalize search Free Digital Factory from running searches

so that it can focus on its core responsibilities


Requirements Shouldn't impact Digital Factory core As transparent as possible to end users Functionally equivalent to internal search Support horizontal scaling Should support extended search use cases

for future improvements


Digital Factory infrastructure

Added support for multiple SearchProvider implementations

You can add your own: one interface, four methods to implement (two, really)

Automatically found and registered by Digital Factory is available in Spring context

Server settings provided to select implementation


Which search engine? Elasticsearch for several reasons:

Open source Built-in distribution / clustering Better support for our use cases Easier to get started with Nicer documentation Easier to work with (RESTful API / JSON)


Architecture Digital Factory module SearchProvider implementation Embeds Elasticsearch but can connect to a

running server Deploys JCR event listeners to automatically

index data changes as they happen


Indexing Only defined node types are indexed Only string, date and j:extractedText

properties are indexed Possible to exclude properties


More indexing Automatically leverages node type

definitions to create Elasticsearch mappings I18n properties => language-specific analyzer Non-text searchable => not analyzed IndexType.NO => not indexed Boost properly supported


Installation / configuration

Deploy module SearchProvider selection Elasticsearch configuration:

Cluster name Indexed node types Excluded properties


A quick look at the data Using elasticsearch-head (

http://mobz.github.io/elasticsearch-head) Requires CORS support (automatically

activated in Dev mode by implementation)

http://mobz.github.io/elasticsearch-head


Joining an existing cluster

Start a separate Elasticsearch instance Change cluster name in settings to join

separate instance cluster Check indices


Benefits Transparent to users as it uses the same

search infrastructure / UI Decouples searches from "normal" Digital

Factory operations Transparent scalability using Elasticsearch

clustering


Current state Initial implementation to validate concept

Indexer Listeners

Available as an Enterprise Edition add-on: talk to your account manager!


Current limitations Only one SearchProvider per server Still requires to convert results to JCR

nodes, in particular to ensure proper permissions


Future Better indexing to improve search performance Avoid going back to JCR nodes to create a

search hit to further decouple from Digital Factory core

Better access to Elasticsearch More powerful search mechanisms


Questions?

JahiaOne 2015 - Search at scale: free Digital Factory from running searches!

Technology

Transcript of JahiaOne 2015 - Search at scale: free Digital Factory from running searches!