Enterprise search in Plone using Solr
by Calvin Hendryx-Parker on Jun 01, 2010
- 2,630 views
Out of the box, Plone includes an integrated and powerful search engine with features such as live search and full text indexing. Sometimes this isn't enough or you need more robust search features to ...
Out of the box, Plone includes an integrated and powerful search engine with features such as live search and full text indexing. Sometimes this isn't enough or you need more robust search features to provide your site visitors with a more custom search experience.
In this talk, Six Feet Up CTO Calvin Hendryx-Parker, will go into the details of implementing Solr with Plone for a large project. Solr is an enterprise search engine that can be deployed alongside of Plone.
Some of the topics to be discussed include:
weighted search
thesaurus
spell check
flexible query parsing
faster search performance
and more...
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 6
- Downloads
- 37
- Comments
- 0
- Embed Views
- Views on SlideShare
- 2,382
- Total Views
- 2,630
frias
XML, JSON, HTTP (REST)
Efficient Replication to other Solr Search Servers
Full Plugin Architecture
HTTP GET returns XML results
Numeric Types, Dynamic Fields, Unique Keys
rich set of debugging tools
Numeric Types, Dynamic Fields, Unique Keys
rich set of debugging tools
still using zope in the middle for this
did the same import with ZCTextIndex and ZCatalog and it crashed and burned at 900k items
except SearchableText which it removes from the catalog
anytime you add an index to the catalog, have to add it to solr also
global or thread local variables usually make it much harder to understand
horrible code readability
could lead to unexpected results, maybe your solr connection isn't there anymore
Six Feet Up embarked on a large project where flexible search features were a great match for Solr.
We shouldn't throw away everything in collective.solr.
allow us to re-factor our connection to Solr
uses the solr schema to determine what columns to index
maintains a persistent connection to external db from a ZODB object
won't be dropped by object deactivations like _v_ methods
won't break when you pass control between treads like thread locals
Pass solr query paramaters directly via the solr_param dictionary.
Requires that some value be passed for "q".
Can be used to access features like weighting of terms in a query.
Pass in a solr_callback function in your query and SolrIndex will call it passing the parsed Solr response object.
Just use the sort_on parameter like you normally would.
ZCatalog falls short on full text indexing when it comes to performance and features
Native ZCatalog indexes are faster than any network bound service.
ZCatalog Indexes share transaction aware ZODB caches.
richer metadata than the wiktionary data