Solr as your search and suggest engine   karan nangru
Upcoming SlideShare
Loading in...5
×
 

Solr as your search and suggest engine karan nangru

on

  • 2,864 views

Session presented at the 6th IndicThreads.com Conference on Java held in Pune, India on 2-3 Dec. 2011.

Session presented at the 6th IndicThreads.com Conference on Java held in Pune, India on 2-3 Dec. 2011.

http://Java.IndicThreads.com

Statistics

Views

Total Views
2,864
Slideshare-icon Views on SlideShare
1,303
Embed Views
1,561

Actions

Likes
0
Downloads
2
Comments
0

2 Embeds 1,561

http://karannangru.wordpress.com 1550
http://ww.karannangru.wordpress.com 11

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NoDerivs LicenseCC Attribution-NoDerivs License

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

    Solr as your search and suggest engine   karan nangru Solr as your search and suggest engine karan nangru Presentation Transcript

    • Solr as your Search andSuggest Engine Karan Nangru 1
    • What is Solr…….• Enterprise search server that takes in data in the form of documents (indexing) - JSON, XML, HTTP binaries• Query (HTTP GET) to fetch the results• Internally – It’s a wrapper over Lucene 2
    • What lured us to Solr• A wrapper over Lucene with predefined extensible features• Jet set go…… (Web application Archive (WAR) format) • Provides cool search and suggest features• Scalable• Maven support 3
    • Setting up the Solr server….• the admin console….• the admin query….• the maven script…. 4
    • Storage Structure…. 5
    • Using Solr @ Java…. 6
    • Configuration and Schema…. 7
    • Tokenizer Factories… 8
    • Token Filter Factories… exam pl e s… 9
    • Solr for Searching• Configuration setup….• Schema setup….• Java client….• JUnit…. example…. 10
    • Solr for Suggestions• Configuration setup….• Schema setup….• Java client….• JUnit…. example…. 11
    • Excess of anything is badThere are various features available but analyze your use case and only use features that you REALLY need…..The more you add, the larger the data, the bulkier the operations, the slower the response time 12
    • The ease of scaling…. 13
    • thank you…Karan NangruSenior Consultant @ Xebia IT ArchitectsTwitter ID: KaranNangruhttp://karannangru.wordpress.com 14