Get flash to fully experience Pearltrees
-- Update am 11.6.2012 Solr hat sich in den letzten Jahren im OpenSource Bereich zum de Facto Standard für Suchserver gemausert. Seit einiger Zeit gibt es eine TYPO3-Extension welche sich zum einen um die Indexierung der Inhalte und zum anderen um die Darstellung der Suche im Frontend kümmert. An dieser Stelle wird beschrieben, wie diese Such eingerichtet werden kann. Solr Extension installieren Auch wenn man meint, dass hier Schritt B vor Schritt A gemacht wird, ist es dennoch sinnvoll, zuerst die Extension zu installieren und danach den Solr Server aufzusetzen.
Blog » Entwicklung » Performante numerische Bereichsanfragen mit Solr 1.4/Lucene 2.9 <img class="size-full wp-image-2422 alignright" title="Suche in Zahlen-Bereichen mit Solr" src="http://blog.sybit.de/wp-content/uploads/2011/04/fotolia_11057585_XS.jpg" alt="Suche in Zahlen-Bereichen mit Solr" width="274" height="245" /> Solr ist eine Enterprise-Suchmaschine, die auf Apache Lucene basiert.
A common need in search applications is suggesting query terms or phrases based on incomplete user input. These completions may come from a dictionary that is based upon the main index or upon any other arbitrary dictionary. It's often useful to be able to provide only top-N suggestions, either ranked alphabetically or according to their usefulness for an average user (e.g. popularity, or the number of returned results). Solr 3.1 includes a component called Suggester that provides this functionality.
Lucene has a custom query syntax for querying its indexes. Unless you explicitly specify an alternative query parser such as DisMax or eDisMax, you're using the standard Lucene query parser by default. Here are some query examples demonstrating the query syntax. Keyword matching Search for word "foo" in the title field. title : foo
Relevancy is the quality of results returned from a query, encompassing both what documents are found, and their relative ranking (the order that they are returned to the user.) Should I use the standard or dismax Query Parser The standard Query Parser uses SolrQuerySyntax to specify the query via the q parameter, and it must be well formed or an error will be returned. It's good for specifying exact, arbitrarily complex queries.
The DisMax query parser is designed to process simple phrases (without complex syntax) entered by users and to search for individual terms across several fields using different weighting (boosts) based on the significance of each field. Additional options enable users to influence the score based on rules specific to each use case (independent of user input). In general, the DisMax query parser's interface is more like that of Google than the interface of the 'standard' Solr request handler.
Skip to end of metadata Go to start of metadata Solr makes it easy for programmers to develop sophisticated, high-performance search applications with advanced features such as faceting (arranging search results in columns with numerical counts of key terms). Solr builds on another open source search technology: Lucene, a Java library that provides indexing and search technology, as well as spellchecking, hit highlighting and advanced analysis/tokenization capabilities. Both Solr and Lucene are managed by the Apache Software Foundation ( www.apache.org) . The Lucene search library currently ranks among the top 15 open source projects and is one of the top 5 Apache projects, with installations at over 4,000 companies.
Nested Queries in Lucene Syntax To embed a query of another type in a Lucene/Solr query string, simply use the magic field name _query_ . The following example embeds a lucene query type:poems into another lucene query: text:"roses are red" AND _query_:"type:poems" Now of course this isn’t too useful on it’s own, but it becomes very powerful in conjunction with the query parser framework and local params which allows us to change the types of queries.
SolrCloud ZooKeeper ClusterJ http://fergiemcdowall.github.com/solrstrap/ http://manifoldcf.apache.org/en_US/index.html http://www.quizmeup.com/quiz/apache-solr-configuration http://www.datastax.com/dev/blog/dse-solr-backup-restore-and-re-index http://rockyj.in/2012/05/08/setting_up_solr.html http://charlesleifer.com/blog/solr-ubuntu-revisited/ http://wiki.apache.org/solr/SolrCloud/ We do not want to have to write a separate init script for Solr. If we are already running Tomcat, and if Tomcat already have an init script, we should deploy Solr using Tomcat. My unanswered questions on Solr Unread articles Miscellaneous Running Apache Solr in a cloud I was having a problem with using wildcard.
Install SOLR 1.4.1 on Ubuntu 10.10 Maven Maverick Multicore using Tomcat 6 Complete Guide Yodi Aditya Researcher + TravellerInstalling Apache Lucene SOLR 1.4.1 in Ubuntu 10.10 using tomcat 6 is easy like in another version. Some changes come in Tomcat 6 path in Ubuntu 10.10. But don't worry, it's not too difficult. If you using ubuntu Karmic Koala 10.04, you can go to my previous article .
The book is focused on the 3.1 version of Solr. The content is divided into ten thematic chapters, each of which consists of a few to several subsections. The book is maintained in the convention cookbook which means that it is not a guide from A to Z about Solr – it is a ready-made solutions to some of the problems that can be encountered while working with Solr. The book will include topics such as:
Almost everyone has seen how the autocomplete feature looks like. No wonder, then, Solr provides mechanisms by which we can build such functionality. In today’s entry I will show you how you can add autocomplete mechanism using faceting. Indeks Suppose you want to show some hints to the user in the on-line store, for example you want to show products name.
In the previous part I showed how the faceting mechanism can be used to achieve the autocomplete functionality. Today I’ll show you how to use a component called Suggester to implement autocomplete functionality. The begining There is one thing that you must know – Suggest component is not available in Solr version 1.4.1 and below. To start using this component you need to download 3_x or trunk version from Lucene/Solr SVN.
Faceted search is the dynamic clustering of items or search results into categories that let users drill into search results (or even skip searching entirely) by any value in any field. Each facet displayed also shows the number of hits within the search that match that category. Users can then “drill down” by applying specific contstraints to the search results. Faceted search is also called faceted browsing, faceted navigation, guided navigation and sometimes parametric search. It’s easiest to understand what faceted search is through an example, appropriately from CNET Reviews, the first website to use Solr even before it had been contributed to Apache by CNET. This example is actually faceted browsing because it started with all digital cameras and not a user search.
Multiple cores let you have a single Solr instance with separate configurations and indexes, with their own config and schema for very different applications, but still have the convenience of unified administration. Individual indexes are still fairly isolated, but you can manage them as a single application, create new indexes on the fly by spinning up new SolrCores, and even make one SolrCore replace another SolrCore without ever restarting your Servlet Container. See MultipleIndexes Solr1.3 Since Solr1.3 , SolrCore can optionally be managed at runtime.