# ElasticSearch Analytics Capabilites

**URL:** <https://discuss.elastic.co/t/elasticsearch-analytics-capabilites/15789>\
**Category:** Elasticsearch\
**Created:** [February 13, 2014, 7:57pm UTC](https://discuss.elastic.co/t/elasticsearch-analytics-capabilites/15789 "2014-02-13T19:57:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Binil\_Thomas](https://avatars.discourse-cdn.com/v4/letter/b/a183cd/32.png) [@Binil\_Thomas](https://discuss.elastic.co/u/Binil_Thomas)\
**Post date:** [February 13, 2014, 7:57pm UTC](https://discuss.elastic.co/t/elasticsearch-analytics-capabilites/15789/1 "2014-02-13T19:57:05Z")

</div>

ES seems to have ability to run analytic queries. I have read about people  
using it as an OLAP solution [1](https://groups.google.com/forum/#!topic/elasticsearch/iTy9IYL23as), although I have not yet read anyone  
describe their experience. In that respect how does ES analytics  
capabilities compare against:

1. Dremel clones [2](http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/36632.pdf) like Impala & Presto (for near real-time, ad hoc  
analytic queries over large datasets)
2. Lambda Architecture [3](http://jameskinley.tumblr.com/post/37398560534/the-lambda-architecture-principles-for-architecting) systems (where queries are known up- front, but  
need to run against a large dataset)

Does anyone here have experience running ES in such usecases, beyond the  
free text searching one ES is well-known for?

Thanks,  
Binil

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5c75a380-3971-45cd-b10d-a91b3b97ecc3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5c75a380-3971-45cd-b10d-a91b3b97ecc3%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\
**Post date:** [February 13, 2014, 10:39pm UTC](https://discuss.elastic.co/t/elasticsearch-analytics-capabilites/15789/2 "2014-02-13T22:39:12Z")

</div>

Hi,

I have to admit I don't know much about these other systems you mentionned.  
Something I can say is that the way these analytics queries are run is  
similar in the sense that they are run over a column-oriented view of the  
data (called fielddata in Elasticsearch). You can also read this thread  
that highlights similarities between Parquet and Lucene doc values (that  
Elasticsearch can use as a fielddata backend) [1](https://groups.google.com/forum/#!topic/elasticsearch/iTy9IYL23as).

Something I would expect Elasticsearch to do well compared to these systems  
is:

- working with strings: because storage is segment-based every term can be  
identified by an ordinal, which can be used to make some computations very  
fast (eg. terms aggregations[2](http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/36632.pdf))
- slicing and dicing data: thanks to its inverted index, Elasticsearch can  
very quickly filter documents that match specific criteria and only run  
analytics on this subset of the data.

The other tools you mentioned probably have pros as well but I don't know  
them enough to be able to tell you what they would bring compared to  
Elasticsearch.

[1](https://groups.google.com/forum/#!topic/elasticsearch/iTy9IYL23as)  
[http://lucene.472066.n3.nabble.com/Parquet-dictionary-encoding-amp-bit-packing-td4090238.html](http://lucene.472066.n3.nabble.com/Parquet-dictionary-encoding-amp-bit-packing-td4090238.html)  
[2](http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/36632.pdf)

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

On Thu, Feb 13, 2014 at 8:57 PM, Binil Thomas [binil.thomas@gmail.com](mailto:binil.thomas@gmail.com)wrote:

> ES seems to have ability to run analytic queries. I have read about people  
> using it as an OLAP solution [1](https://groups.google.com/forum/#!topic/elasticsearch/iTy9IYL23as), although I have not yet read anyone  
> describe their experience. In that respect how does ES analytics  
> capabilities compare against:
> 
> 1. Dremel clones [2](http://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/36632.pdf) like Impala & Presto (for near real-time, ad hoc  
> analytic queries over large datasets)
> 2. Lambda Architecture [3](http://jameskinley.tumblr.com/post/37398560534/the-lambda-architecture-principles-for-architecting) systems (where queries are known up- front, but  
> need to run against a large dataset)
> 
> Does anyone here have experience running ES in such usecases, beyond the  
> free text searching one ES is well-known for?
> 
> Thanks,  
> Binil
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/5c75a380-3971-45cd-b10d-a91b3b97ecc3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5c75a380-3971-45cd-b10d-a91b3b97ecc3%40googlegroups.com)  
> .  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
Adrien Grand

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j61JVv9p8csvBkD6fGba6u%3D59g%3DhzXBVrf%2BsqeX%3DZ82HA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAL6Z4j61JVv9p8csvBkD6fGba6u%3D59g%3DhzXBVrf%2BsqeX%3DZ82HA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:50am UTC](https://discuss.elastic.co/t/elasticsearch-analytics-capabilites/15789/3 "2017-07-06T01:50:22Z")

</div>


