Data::SearchEngine::ElasticSearch - ElasticSearch support for Data::SearchEngine


version 0.21


    use Data::SearchEngine::Query;
    use Data::SearchEngine::ElasticSearch;

    my $dse = Data::SearchEngine::ElasticSearch->new(
        servers => [ '' ]

    my $query = Data::SearchEngine::Query->new(
        index => 'tweets',
        page => 1,
        count => 10,
        order => { _score => { order => 'asc' } },
        type => 'query_string',
        facets => {
            etype => { terms => { field => 'etype' } },
            author_organization_literal => { terms => { field => 'author_organization_literal' } },
            author_literal => { terms => { field => 'author_literal' } },
            source_literal => { terms => { field => 'source_literal' } },

    my $results = $dse->search($query);


Data::SearchEngine::ElasticSearch is a backend for Data::SearchEngine. It aims to generalize the features of ElasticSearch so that application authors are insulated from some of the differences betwene search modules.


This module is opinionated. ElasticSearch's query language and features are powerful and difficult to reign in. Therefore this module has taken some steps to bring things toward a more central feature set.


ElasticSearch's query DSL is large and complex. It is not well suited to abstraction by a library like this one. As such you will almost likely find this abstraction lacking. Expect it to improve as the author uses more of ElasticSearch's features in applications.


The _index and _version keys will both be populated in the returned Data::SearchEngine::Item.


Setting debug to a true value will cause <explain> to be set when the query is sent to ElasticSearch. You can find the explanation by examining the raw attribute of the Data::SearchEngine::Results object.


It is expected that if your Data::SearchEngine::Query object has any query set then it must also have a type.

The query is then passed on to ElasticSearch thusly:

        # ...
        query => { $query->type => $query->query }
        # ...

So if you want to do a query_string query, you would set up your query like this:

    my $query = Data::SearchEngine::Query->new(
        # ...
        type => 'query_string',
        query => { query => 'some query text' }
        # ...

See the documents for ElasticSearch's DLS for more details.


ElasticSearch wants an index and type for each Item that is indexed. It is expected that you will populate these values in the item thusly:

  my $item = Data::SearchEngine::Item->new(
    id => $something,
    values => {
        index => 'twitter',
        type => 'tweet',
        # and whatever else


If you set multiple filters they will be ANDed together. If you want to change this behavior then you can supply an additional argument to the query method:

  $dse->search($query, 'or');

This defaults to 'and'.

Facets & Filters

If you use facets then any filters will be copied into the facet's facet_filter so that the facets are limited similarly to the results.



The servers to which we'll be connecting.


The transport to use. Refer to ElasticSearch for more information.


add ([ $items ])

Add items to the index. Keep in mind that the Data::SearchEngine::Item should have values set for index and type.


Returns the underlying ElasticSearch implementation.

present ($item)

Returns true if the Data::SearchEngine::Item is present. Uses the item's id.

remove_by_id ($item)

Remove the specified item from the index. Uses the item's id.

search ($query)


find_by_id ($index, $type, $id)

Find a document by it's unique id.


Cory G Watson <>


This software is copyright (c) 2012 by Cold Hard Code, LLC.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.