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

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Solr as your search and suggest engine karan nangru

2,902
views

Published on

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

Published in: Technology, Design

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,902
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Solr as your Search andSuggest Engine Karan Nangru 1
  • 2. 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
  • 3. 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
  • 4. Setting up the Solr server….• the admin console….• the admin query….• the maven script…. 4
  • 5. Storage Structure…. 5
  • 6. Using Solr @ Java…. 6
  • 7. Configuration and Schema…. 7
  • 8. Tokenizer Factories… 8
  • 9. Token Filter Factories… exam pl e s… 9
  • 10. Solr for Searching• Configuration setup….• Schema setup….• Java client….• JUnit…. example…. 10
  • 11. Solr for Suggestions• Configuration setup….• Schema setup….• Java client….• JUnit…. example…. 11
  • 12. 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
  • 13. The ease of scaling…. 13
  • 14. thank you…Karan NangruSenior Consultant @ Xebia IT ArchitectsTwitter ID: KaranNangruhttp://karannangru.wordpress.com 14