Kiriaki,
               Be aware the analyzers/filters for anything other than very 
simple cases usually come in pairs, one for indexing and one for searching. It 
is important to understand that if a field is analyzed/filtered in one way 
(lowercase filter is a simple case) for indexing this will have an impact on 
how your search performs as it (may) go through analysis/filtering before it 
gets to the part where terms are matched.
               A good place to check what is going on is the SOLR admin 
interface (http://127.0.0.1:8080/solr/search/admin/schema.jsp for a browser 
that gives you info on all your fields and how they are analyzed and filtered.
               Also the http://127.0.0.1:8080/solr/search/admin/analysis.jsp 
page is good for checking what is happening to an input as it goes through 
analysis/filtering for both the index and search chains.
               As an example select the field name “text” with a field value of 
“wi-fi” for indexing and “wi-fi” for searching, when you hit the analyze button 
you will see the results of the two chains. In this case the index chain has 
the terms wi,fi and wifi and the search chain has the terms wi and fi. This in 
combination with other filters (i.e. stemming) will determine what terms are 
available for searching and what the results will be for a given search.
               For your case I would assume that if it you want a simple query 
over a text field the index and analysis chain should produce the same results 
for a given input, but this will be dependent on the exact query that is issued 
to SOLR and the parameters that are passed (this is one area I need to look at 
in Dspace).

               One word of caution – this is a very big topic ☺

Regards,
               Ben

------------------------------------------------------------------
Dr Ben Ryan
Jorum Technical Manager

5.12 Roscoe Building
The University of Manchester
Oxford Road
Manchester
M13 9PL
Tel: 0160 275 6039
E-mail: 
[email protected]<https://outlook.manchester.ac.uk/owa/redir.aspx?C=b28b5bdd1a91425abf8e32748c93f487&URL=mailto%3abenjamin.ryan%40manchester.ac.uk>
------------------------------------------------------------------

From: Kiriaki Roditi [mailto:[email protected]]
Sent: 20 May 2013 14:58
To: [email protected]
Subject: [Dspace-tech] Help with configuring SOLR to use a specific search 
analyzer

Hello DSpace community,

I am trying to set SOLR to use the Greek analyzer for searches performed in 
Mirage, DSpace version 3.1.
Setting the analyzer property in dspace.cfg to search.analyzer = 
org.apache.lucene.analysis.el.GreekAnalyzer seems to be working only for jspui' 
s search aspect,
so after a bit of searching and reading apache wikis, I performed the following 
actions:

 - uncommented the following in [dspace-src]/dspace/solr/search/conf/schema.xml

<fieldType name="text_greek" class="solr.TextField">
      <analyzer class="org.apache.lucene.analysis.el.GreekAnalyzer"/>
</fieldType>
- rebuilt dspace
- stopped tomcat
- cleared tomcat's cache
- recreated indexes several times running: index-init, update-discovery-index 
and index-init, update-discovery-index -b

but it does not seem to work. Am I missing something? Any suggestions would be 
more than welcome!

Regards,

Kiriaki Roditi
ELiDOC Systems & Services
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

Reply via email to