We are at times having some difficulty achieving a 'successful' replication.
Our Operations personnel have reported the following behavior (which I cannot
attest to): A master has a set of segment files (let's say 25). A slave then
polls the master, get the list of segment files that differ an
ter for other purposes, if you
just want to remove possessives and don't need worddelimiterfilter's other
features, look below.
2. you can instead use EnglishPossessiveFilterFactory, which only does this
exact thing (remove 's) and nothing else.
On Wed, Oct 19, 2011 at
We utilize a comprehensive dictionary of English words, place names, surnames,
male and female first names, ... you get the point. As such, the possessive
plural forms of these words are recognized as 'misspelled'.
I simply thought that 'turning on' this option for the WordDelimiterFactory
wou
We service about 25K of each particular query type per hour per server. QTime
*averages* less than a second; however, there always a few (1-10) whose QTimes
go way above (10 - 500 seconds) the average. If I harvest these queries from
the log an re-execute them they of course execute sub-second
It generally helps if your solrconfig is correct. Thank you for your
tolerance.
-Original Message-
From: Herman Kiefus [mailto:herm...@angieslist.com]
Sent: Thursday, September 01, 2011 10:15 AM
To: solr-user@lucene.apache.org
Subject: MoreLikeThis assumptions
Given a document id:n
operational.
(11/09/01 23:24), Herman Kiefus wrote:
> class="org.apache.solr.handler.component.MoreLikeThisComponent">
>
>mlt
>
>
>
> but ends up returning a 500 error on a core reload. What is an appropriate
> configuration entry
I've begun tinkering with MLT using the standard request handler. The Wiki
also suggests using the MoreLikeThis handler directly, but apparently, this is
not in the default configuration (as I recall, I haven't removed anything from
solrconfig.xml as shipped). For example:
http://devsolr03:89
Given a document id:n show me those other documents with similar values in the
'Name' field:
http://devsolr03:8983/solr/primary/select?q=id:182652&fl=id,Name,score&mlt=true&mlt.fl=Name
My assumption is the above query will generate the desired outcome. It does;
however, given a different docum
u considered having two dictionaries and using ajax to query them both
and intermingling the results in your suggestions? It'd be some work, but I
think it might accomplish what you want.
Best
Erick
On Tue, Aug 23, 2011 at 1:48 PM, Herman Kiefus wrote:
> To close, I found this article
you can see what I'm getting at: a source for the
> spellchecker that only contains correct spelled terms plus proper names;
> should I have gone about this in a different way?
>
> -Original Message-
> From: Stephen Duncan Jr [mailto:stephen.dun...@gmail.com]
The angle that I am trying here is to create a dictionary from indexed terms
that contain only correctly spelled words. We are doing this by having the
field from which the dictionary is created utilize a type that employs
solr.KeepWordFilterFactory, which in turn utilizes a text file of known
We employ one 'indexing' master that replicates to many 'query' slaves. We
have also recently introduced spellchecking/DYM. It appears that replication
does not 'cover' the spellchecker index. Do I understand this correctly?
Further, we have seen where 'buildOnCommit' will cause the spellchec
My objective is to end up with a field that can be used to build the spellcheck
dictionary; however, that field will only contain correctly spelled terms other
than those terms originating from two other 'proper name' fields.
I thought I had this working, but feedback from a separate thread seem
correct spelled terms plus proper names; should
I have gone about this in a different way?
-Original Message-
From: Stephen Duncan Jr [mailto:stephen.dun...@gmail.com]
Sent: Monday, August 22, 2011 9:30 AM
To: solr-user@lucene.apache.org
Subject: Re: Text Analysis and copyField
On Mon, Aug 2
Is my thinking correct?
I have a field 'F1' of type 'T1' whose index time analysis employs the
StopFilterFactory.
I also have a field 'F2' of type 'T2' whose index time analysis does NOT employ
the StopFilterFactory.
There is a copyField directive source="F1" dest="F2"
F2 will not contain any
the SOLR-2010 patch.
James Dyer
E-Commerce Systems
Ingram Content Group
(615) 213-4311
-Original Message-
From: Herman Kiefus [mailto:herm...@angieslist.com]
Sent: Wednesday, August 17, 2011 4:55 PM
To: solr-user@lucene.apache.org
Subject: RE: Solr spellcheck and multiple collations
Thank
w how many hits each collation will return, also
specify "spellcheck.collateExtendedResults=true"
- See http://wiki.apache.org/solr/SpellCheckComponent#spellcheck.maxCollations
for more information
James Dyer
E-Commerce Systems
Ingram Content Group
(615) 213-4311
-----Original Me
schema and config?
I believe that's how collation is: the best match, only one.
2011/8/17 Herman Kiefus
> After a bit of work, we have 'spellchecking' up and going and we are
> happy with the suggestions. I have not; however, ever been able to
> generate more than
After a bit of work, we have 'spellchecking' up and going and we are happy with
the suggestions. I have not; however, ever been able to generate more than one
collation query. Is there something simple that I have overlooked?
While I can't be as specific as other here will be, we encountered the
same/similar problem. We simply loaded up our servers with 48GB and life is
good. I too would like to be a bit more proactive on the provisioning front
and hopefully someone will come along and help us out.
FWIW and I'm su
e future point in time (which I supposed
> might also be called Solr 4 in the future -- won't that be confusing!)
>
> -Original Message-
> From: Herman Kiefus [mailto:herm...@angieslist.com]
> Sent: Wednesday, August 17, 2011 2:55 PM
> To: solr-user@lucene.apache.org
>
My origination uses Solr 4 because of our geospatial requirements. What
insight can you share (if any) regarding moving forward to a later nightly
build? Or, for those of you using 4.0 in a Production setting, when is it that
you move ahead?
22 matches
Mail list logo
