Further without the NRT features present what's the closest I can
expect to real time for the typical use case (obviously this will vary
but the average deploy). One hour? One Minute? It seems like there are
a few hacks to get somewhat close. Thanks so much.
Depends a lot on the
are lowercased during analysis.
An functional alternative, of course, is to have the client
lowercase the query expression before requesting to Solr
(careful, though - consider AND/OR/NOT).
Erik
On Jul 1, 2008, at 8:14 PM, George Aroush wrote:
Hi Folks,
Can someone tell me what
Hi Folks,
Has anyone created schema.xml for languages other then English? I like to
see a working example mainly for CJK, German and French. If you have can
you share them?
TO get me started, I created the following for German:
fieldtype name=myfieldtype class=solr.TextField
analyzer
@lucene.apache.org
Subject: Re: schema.xml for CJK, German, French, etc.
On Jul 2, 2008, at 9:16 PM, George Aroush wrote:
Has anyone created schema.xml for languages other then English?
Indeed.
I like to
see a working example mainly for CJK, German and French.
If you have
can you
Hi Folks,
Can someone tell me what I might have setup wrong? After indexing my data,
I can search just fine on, let say sol* but not on Sol* (note upper case
'S' vs. lower case 's') I get 0 hits.
Here is my customize schema.xml setting:
fieldType name=text class=solr.TextField
Hi folks,
Has anyone managed to get Solr 1.2 to run under WebSphere 6.1? If so, can
you share your experience, what configuration, settings, etc. you had to do.
Someone asked this questions earlier this month, but I don't see anyone
followed up -- so I'm asking again since I have this need too.
I was going through some old emails on this topic. Rafael Rossini
figured out how to run multiple indices on single instance of jetty
but it has to be jetty plus. I guess jetty doesn't allow this? I
suppose I can add additional jars and make it work but I
haven't tried
that. It'll
