• Like
  • Save
Elastic search apache_solr
Upcoming SlideShare
Loading in...5
×
 

Elastic search apache_solr

on

  • 4,894 views

 

Statistics

Views

Total Views
4,894
Views on SlideShare
4,886
Embed Views
8

Actions

Likes
6
Downloads
98
Comments
0

3 Embeds 8

http://s.medcl.net 6
http://s.medcl.com 1
http://darya-ld1.linkedin.biz 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Elastic search apache_solr Elastic search apache_solr Presentation Transcript

    • ElasticSearch vs. Apache Solr last update Dec 2011 An experiment to compare  ElasticSearch with Apache Solr From Peter.Karich@pannous.info
    • Preface
      • Comments and suggestions should go to my blog  
      •  
        • This document is based on my personal oppinion and experience with Jetslide  where I moved from Solr and several other projects based on ElasticSearch
        • This document should not be used to show that one of the projects is 'bad'. Keep in mind that both projects are rapidly evolving and you should always make your own tests if a (software) product fits to your use case / company.
    • Similarities of ElasticSearch (ES) and Solr
      • Both software systems are:
        • Powerful search servers based on Lucene 3.5:
          • ElasticSearch 0.18.5
          • Apache Solr 3.5
        • Both are free software and stand under Apache License 2
      • Both systems can send JSON over HTTP for indexing and querying. Both support advanced Lucene queries and more.
    • What ES offers and Solr not (so well)
        • ES is distributed        
          • easy sharding ('splits' one index into smaller)
          • easy replication ('copies' one index to multiple nodes)
          • adding / removing a node is simple; indices will move accordingly
          • easy cloud support for amazon (S3, discovery via API)
          • support for GigaSpaces, Coherence and Terracotta
        • Some Solr features are not supported in 'distributed mode' and there are several methods (no one is really easy) to do it
        • ES is realtime and distributed : just specify latency via API
    • ... what ElasticSearch offers (2)
        • The full JSON doc can be nested and stored within the index in one field called _source (even compressed).       Re-indexing simple
        • Query via JSON (or url). Use curl or ElasticSearch-Head
        • When indexing you specify:
          • the index
          • the id
          • the type - this makes:
        • multi-tenancy  easy. A simple API call to create/delete an index. Solr multi core is more complicated ...
    • ElasticSearch - Head     (similar to Solr Admin page)
    • ... what ElasticSearch offers (3)
        • ES introduces concept of ' Gateway ' for long term persistency
          • define index storage (in-memory, on filesystem ...)
          • when ES crashes it can recover the index storage from this gateway (the 'availability' system). Even if index storage was in-memory.
          • For amazon you can use S3 as gateway
        • ES supports complete scripting while querying to do stats, facets etc.
    • ES lacks ...
        • 100% documentation and always working query examples
          • solve this via freenode and ask!
        • Only one main contributer. No commercial support
          • But strong community (again: freenode + google groups)
          • But Shay is working full time on ES and ES has a strong community. E.g. community developed clients for several different languages
          • Shay has a strong background in 'search'. He wrote Compass
    • ES lacks ...
        • No Autowarming Queries (see issue 1006 )
        • No XML support
        • ES has no facet pagination. See issue  1044
        • ES has no field collapsing. See issue  256
        • ES has no Date Math
        • ES has no separate smaller client jar for Java projects
        • ES has no spell checking plugin. See issue  911
    • When to use ElasticSearch
      • You should use it when
        • Your index is big or realtime or both
        • You have several indices or
        • A multi tenancy requirement.
        • You want to save administration effort and cost
      • And when shouldn't you use ElasticSearch?
        • If your company already uses Solr and no massive indexing is required, you have small indices or no realtime updates are required.
        • You company does not allow it due to riscs
    • ElasticSearch Resources
      • Documentation
        • Search directly  elasticsearch.org
        • groups.google.com/a/elasticsearch.com/group/users
        • Freenode channel #elasticsearch ('group chat')
        • Twitter: twitter.com/elasticsearch
        • Code and Issues:  github.com/elasticsearch/elasticsearch
      • Nice Utilities/Apps
        • ElasticSearch-Head
        • ElasticSearch-BigDesk
        • Logstash - a log indexer built with ES and jruby:  code.google.com/p/logstash
    • Solr Resources
        • A slide which points out how hard distributed Solr/Lucene is
        • Solr Wiki
        • Solr & DistributedSearch