Hi,
This is how we implement our autocomplete feature, excerpt from
schema.xml
-First accept the input as is without alteration
-Lowercase the input, and eliminate all non a-z0-9 chars to normalize
the input
-split into multiple tokens with EdgeNGramFilterFactory upto a max of
100 chars, all
Hi,
I have solr with jetty as server application running on Linux.
Could anyone please tell me the changes i need to make to integrate Tomcat with
solr on Linux.
Thanks,
Sandip
--- On Mon, 7/7/08, Benson Margulies [EMAIL PROTECTED] wrote:
From: Benson Margulies [EMAIL PROTECTED]
Subject:
Take a look at http://wiki.apache.org/solr/SolrTomcat
Please avoid replying to an older message when you're starting a new topic.
On Tue, Jul 8, 2008 at 4:36 PM, sandeep kaur [EMAIL PROTECTED]
wrote:
Hi,
I have solr with jetty as server application running on Linux.
Could anyone please
thanks and sorry, i will take care of this next time
--- On Tue, 8/7/08, Shalin Shekhar Mangar [EMAIL PROTECTED] wrote:
From: Shalin Shekhar Mangar [EMAIL PROTECTED]
Subject: Re: Integrate Solr with Tomcat in Linux
To: solr-user@lucene.apache.org, [EMAIL PROTECTED]
Date: Tuesday, 8 July,
Hi,
I have downloaded the trunk version today and I´m having problems with the
SpellCheckComponent. Its any known bug?
This is my configuration:
#
searchComponent name=spellcheck
Hi Roberto,
1. Why do you have those asterisk characters in your schema field
definition?
2. Did you do a spellcheck.build=true before issuing the first spell check
request?
Also, as per the latest docs on the wiki (
http://wiki.apache.org/solr/SpellCheckComponent ), the defaults section
should
When I made:
http://localhost:8080/solr/spellCheckCompRH?q=*:*spellcheck.q=ruckspellcheck=true
I have this exception:
Estado HTTP 500 - null java.lang.NullPointerException at
org.apache.solr.handler.component.SpellCheckComponent.getTokens(SpellCheckComponent.java:217)
I see this all the
Hi,
I already haved aked this, but I didn't get any good answer, so I will try
again. I need to pre-process a stored field before it is saved. Just like a
field that is gonna be indexed. I would be good to apply an analyzer to this
stored field.
My problem is that I have to send to solr html
Erik Hatcher schrieb:
Mattias,
Nice start!
One comment
In test.html:
new $sj.solrjs.Manager({solrUrl:http://localhost:8983/solr/select});
It would be better to omit the /select from the base URL. Consider
Solr rooted at a particular URL without the request handler mapping
attached
Hi,
Sorry if this question sounds daft but I was wondering if there was
anything built into Solr that allows you to automate the creation of new
indexes once they reach a certain size or point in time. I looked briefly
at the documentation on CollectionDestribution, but it seems more
On Tue, 8 Jul 2008 10:20:15 -0300
Hugo Barauna [EMAIL PROTECTED] wrote:
Hi,
I already haved aked this, but I didn't get any good answer, so I will try
again. I need to pre-process a stored field before it is saved. Just like a
field that is gonna be indexed. I would be good to apply an
Shalin Shekhar Mangar wrote:
Hi Geoff,
I can't find anything in the code which would give this exception when both
q and spellcheck.q is specified. Though, this exception is certainly
possible when you restart solr. Anyways, I'll look into it more deeply.
great, thanks.
There are a few
nothing to automatically create a new index, but check the multicore
stuff to see how you could implement this:
http://wiki.apache.org/solr/MultiCore
On Jul 8, 2008, at 10:25 AM, Willie Wong wrote:
Hi,
Sorry if this question sounds daft but I was wondering if there
was
anything built
Hi Willie,
If you want to have backups (point-in-time snapshots) then you'd need
something similar to the snapshooter script used in replication. I believe
it creates hard links to files of the current index in a new directory
marked with the timestamp. You can either use snapshooter itself or
If all you are doing is stripping text from HTML, the best option is
probably to just do that on the client *before* you send it to solr.
If you need to do something more complex -- or that needs to rely on
other solr configurations you can consider using an
UpdateRequestProcessor. Likely
re-reading your post...
Shalin is correct, just use the snapshooter script to create a point-
in-time snapshot of the index. The multicore stuff will not help with
this.
ryan
On Jul 8, 2008, at 11:09 AM, Shalin Shekhar Mangar wrote:
Hi Willie,
If you want to have backups (point-in-time
The spellcheck.q parameter is optional. However, the q parameter is
compulsory. So you can write q=macrosoft and avoid spellcheck.q altogether.
The difference behind it is that spellcheck.q is used if present and it uses
the query analyzer of the Solr field used to build the index whereas, the q
Hi Daniel,
Thanks for the code. I just did observe that you have
EdgeNGramFilterFactory. I didnt find it in the 1.2 Solr version. Which version
are you using for this. 1.3 isnt out yet rite. Is there any other production
version of Solr available that I can use?
Regards
Sundar
deletequery*:*/query/delete
will wipe all data in the index...
On Jul 8, 2008, at 12:05 PM, Willie Wong wrote:
Thanks Sahlin and Ryan for your posts...
I think the snapshooter will work fine for creating the indexes and
then I
can use the multicore capabilities to make them available to
He must be using a nightly build of Solr 1.3 -- I think you can consider
using it as it is quite stable and close to release.
On Tue, Jul 8, 2008 at 10:38 PM, sundar shankar [EMAIL PROTECTED]
wrote:
Hi Daniel,
Thanks for the code. I just did observe that you have
hossman wrote:
This is Issue #1 regarding trying to use query time multi word synonyms
discussed on the wiki...
The Lucene QueryParser tokenizes on white space before giving any
text to the Analyzer, so if a person searches for the words sea biscit
the analyzer will be given the
Hi,
As i am running tomcat after copying the solr files to appropriate tomcat
directories, i am getting the followin error in the catalina log:
Jul 8, 2008 10:30:02 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The Apache Tomcat Native library which allows optimal performance in
On Tue, 8 Jul 2008 21:10:51 +0530
Shalin Shekhar Mangar [EMAIL PROTECTED] wrote:
Also note that you'll need to specify spellcheck.build=true only on the
first request when it will build the spell check index. The subsequent
requests need not have spellcheck.build=true.
as a matter of fact,
On Tue, 8 Jul 2008 12:05:45 -0400
Willie Wong [EMAIL PROTECTED] wrote:
I think the snapshooter will work fine for creating the indexes and then I
can use the multicore capabilities to make them available to users one
final question though, after snapshot has been created is there a way
Yes, SOLR-350 added that capability. Look at
http://wiki.apache.org/solr/MultiCore for details.
On Wed, Jul 9, 2008 at 6:26 AM, Norberto Meijome [EMAIL PROTECTED]
wrote:
On Tue, 8 Jul 2008 12:05:45 -0400
Willie Wong [EMAIL PROTECTED] wrote:
I think the snapshooter will work fine for
The context 'solr' is not initialized. The most likely reson is that
you have not set the solr.home correctly.
--Noble
On Wed, Jul 9, 2008 at 3:24 AM, sandeep kaur [EMAIL PROTECTED] wrote:
Hi,
As i am running tomcat after copying the solr files to appropriate tomcat
directories, i am
set the solr home folder such that-
If you are using jndi name for solr.home or command line argument for
solr.home, then it will look for conf and lib folders under that folder.
If you are not using jndi name, then it looks for solr/conf and solr/lib
folders under current directory which is the
27 matches
Mail list logo
