Suggester configuration - solr

I am a beginner i already installed solr 3.4 using Tomcat. i installed it for my undergrad thesis . i am reading the cookbook 3.1 and Lucid imagination 1.4. but i am facing problem in configuration suggester component which i found in cook book 3.1. I have written the xml code in config xml file and i tried also the solr wiki code but, it is giving me error when i am quering http://localhost:8983/solr/suggester/?q=a . My question is
. how could i resolve this
. Does 3.4 version have suggester component, though i have checked.
. Is there any version clash issue in solr
It will be great help for me to proceed if you enlighten.

Suggester was included with Solr 3.1 and above.
Check out the references, which explains it better -
http://lucidworks.lucidimagination.com/display/solr/Suggester
http://solr.pl/en/2010/11/15/solr-and-autocomplete-part-2/

Related

Upgrading Solr 6 to use Log4j 2.x

Is it possible to upgrade Solr 6 to use Log4j 2.x?
We have some external dependencies on Solr 6 but would like to upgrade Log4j to the latest.
From the Apache documentation
Apache Solr releases prior to 7.4 (i.e. Solr 5, Solr 6, and Solr 7
through 7.3) use Log4J 1.2.17 which may be vulnerable for installations
using non-default logging configurations that include the JMS Appender,
see
https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126
for discussion.
A good alternative would be to replace log4j 1.2.17 with reload4j, which is a direct plugin replacement for the log4j jar file. It was developed by one of the companies that developed the original log4j project in response to its recently reported vulnerabilities. You can find more information at the Github project
I am aware of at least one OpenSource project (Alfresco) that is using it successfully.

Alfresco 5.0.c + SOLR4, custom properties not indexed

I'm using Alfresco 5.0.c. Recently I've upgraded from Solr 1.4 to Solr 4 (locally and on server).
The problem I've faced with is that custom properties are not indexed anymore.
In Solr 1.4 to index custom properties I was using search.get.config.xml file with following content:
<search>
<default-operator>AND</default-operator>
<default-query-template>
%(cm:name cm:title cm:description
<!--custom properties-->
xz:personStatus xz:username xz:typeName xz:orgUnit xz:fullName
TEXT TAG)
</default-query-template>
</search>
But it seems that for Solr 4 this approach doesn't work.
How I can tell Solr 4 to index custom properties?
Another related question.
I installed clean version of alfresco 5.0.c using maven sdk and found out that out of the box it uses solr 1.4 not solr 4 as it was advertized.
In pom.xml of solr artifact-id is alfresco-solr not alfresco-solr4.
Do I miss something?
In my experience I installed Alfresco community 5.0.c using the setup wizard and, as stated in the docs Alfresco SolR4 installation and configuration
The Solr 4 search subsystem is installed by default when you install Alfresco One 5.0 using the setup wizards (installer)
I can assure you that my custom properties are successfully indexed.
Inspecting the Alfresco nexus repository I can see that the correct dependency for 5.0.c is alfresco-solr, whereas under the org.apache.solr.apache-solr branch there is a latest 1.4.1-alfrescopatched-20141112 dependency
For more info take a look here Alfresco SDK 2.0.0

Problem in compiling LocalSolr

I am trying to install LocalSolr following the instruction here:
http://www.gissearch.com/node/16
Unfortunately things are not working well.
In the document, it says:
To install these into solr simply copy the following jars to solr's lib directory.
located in apache-solr-1.*/example/solr/lib
I have noticed that I don't have a folder called "lib" under example/solr, so I built it myself and copied all the mentioned files to it.
And I went to the next step which was altering solrconfig.xml and schema.xml as instructed in here: http://www.gissearch.com/localsolr
and restarted my ApacheSolr, but got the following error:
org.apache.solr.common.SolrException: Error loading class 'com.pjaol.search.solr.component.LocalSolrQueryComponent'
I can't figure out how to fix this problem so I would appreciate the help.
Solr includes official spatial search functionality as of version 3. Based on my experience running Websolr, I recommend you upgrade to Solr 3.3 rather than wrestle with LocalSolr.

Solr 3.1 Admin Interface

I am using Solr 1.4 , by default it comes with web application deployed as "solr.war" in webapps directory in example .
I tried to upgrade to solr 3.1 , but this vesrion (3.1) doesn't have attached web admin interface ,
I copied the solr.war from 1.4 and put it in webapps in 3.1
but this will lunch the 1.4 version of solr rather than 3.1 , I wanted to use edismax feature in 3.1 and other features and improvements ,
Please how can I use ediamx or give me regular steps to upgrade to solr 3.1 or even compile from source !!!
Thank you
Solr 3.1 does have a web admin interface. The web application archive is in the dist directory of the official distribution, the file is named apache-solr-3.1.0.war
download the source package for 3.1
and run "ant example" to build the example solr application
the new war for 3.1 should be under solr/example/webapp dir.
you will need to add the following config in your solrconfig.xml
<luceneMatchVersion>LUCENE_31</luceneMatchVersion>
also make sure your "unique id" field in schema.xml is of type string

Issue with Apache camel 2.4 version

This is an issue when I change the camel version from 1.6 to 2.4.
I wanted to use a method userOriginaLmessage which was not supported in 1.6. Hence I starte using camel 2.4 version. The code is getting compiled. But when I deploy it in Fuse ESB environment I get below error.
Unexpected exception parsing XML document from class path resource [camel-route.xml]; nested exception is java.lang.VerifyError:
Can you please help me on this ? What can be the issue.
Thanks in advance for the help.
Is there any more error message showing up than what you posted? Seems a bit lacking in information :)
There were a ton of changes from 1.6 to 2.4. You should take a look at the Camel 1.x -> 2.x migration guide if you have not done so already:
http://fusesource.com/docs/router/2.2/migration/index.html

Resources