you should look into this http://wiki.apache.org/solr/FunctionQuery
simon
On Fri, Jan 7, 2011 at 3:59 PM, dante stroe wrote:
> Hello,
>
> What I am trying to do is build a personalized search engine. The aim
> is to have the resulting documents' scores depend on users' preferences.
> I've al
I use a script to generate the appropriate solr.xml for each host according to
a config file. You could also prepare separate files and create a soft link
from solr.xml to the appropriate one on each host.
Ephraim Ofir
-Original Message-
From: Lance Norskog [mailto:goks...@gmail.com]
Sorry for the delay, Yahoo tagged my messages as spam and blocked them. I am
resending.
The index seems ok on the master.
In the meanwhile I manually ran a replication on one of the slaves and the
whole index got copied and "added" to the previous index. I had to manually run
RELOAD for that c
Thanks Lance for mentioning the MergePolicies and specifically this one
contributed by LinkedIn.
2011/1/8 Lance Norskog
> There are always slowdowns when merging new segments during indexing.
> A MergePolicy decides when to merge segments. The older MergePolicies
> followed a strategy which is
> The older MergePolicies followed a strategy which is quite disruptive in an
> NRT environment.
Can you elaborate as to why (maybe we need to place this in a wiki)?
If large merges are running in their own thread, they should not
disrupt queries, eg, there won't be CPU contention. The IO conten
I have a couple of questions regarding Solr usage:
1. Certain requests can be sent to different paths (handlers?). For
example, the MoreLikeThis component can being sent to either
/select or /mlt.
I have found these two links in the Solr wiki:
http://localhost:8983/solr/mlt?q=id:U
Has anyone found a way to have multiple properties (override & default)? What
I'd like to create is a default property with an override property that usually
wouldn't be set, but would be set as a JVM parameter if I want to turn off
replication on a particular index on a particular server. I t
> 1. Certain requests can be sent to
> different paths (handlers?). For
> example, the MoreLikeThis component
> can being sent to either
> /select or /mlt.
>
> I have found these two links in the Solr wiki:
>
> http://localhost:8983/solr/mlt?q=id:UTF8TEST&mlt.fl=manu,cat&mlt.mindf=
On 1/7/2011 2:57 AM, supersoft wrote:
have deployed a 5-sharded infrastructure where: shard1 has 3124422 docs
shard2 has 920414 docs shard3 has 602772 docs shard4 has 2083492 docs shard5
has 11915639 docs Indexes total size: 100GB
The OS is Linux x86_64 (Fedora release 8) with vMem equal to 7872
These are definitely server grade machines.
There aren't any desktops I know of (that aren't made for HD video
editing/rendition) that ever need that kind of memory.
Dennis Gearon
Signature Warning
It is always a good idea to learn from your own mistakes. It is usually a
bet
On 01/09/2011 04:05 PM, Ahmet Arslan wrote:
>> ���1. Certain requests can be sent to
>> different paths (handlers?). For
>> � � � example, the MoreLikeThis component
>> can being sent to either
>> � � � /select or /mlt.
>>
>> I have found these two links in the Solr wiki:
>>
>> http://localhost:898
Yes, the replication system sometimes leaves previous files. They do
not get 'added' to the index. The 'segment' files describe which
segment files are part of the index.
The query servers should have query caches turned on, and the indexer
should have them turned off. Those and the replication se
Ok. I was talking about what tools are available now- much better
things are in the NRT work. I don't know how merges work now, in re
multitasking and thread contention. Most of the Solr sites I know of
have much larger indexes than ram and expect everything to work
smoothly.
Lance
On Sun, Jan 9,
On Sat, Jan 8, 2011 at 3:44 AM, Burton-West, Tom wrote:
> Hello all,
>
> We are getting intermittent socket timeout errors (see below). Out of about
> 600,000 indexing requests, 30 returned these socket timeout errors. We
> haven't been able to correlate these with large merges, which tends to
On 10.01.2011, at 08:16, Dennis Gearon wrote:
> Anyone have any experience using this library?
>
> http://us3.php.net/solr
>
Yeah. it works quite well.
However imho the API is a maze. Also its lacking critical stuff like escaping
and nice to have stuff like lucene query parsing/rewriting.
re
I have made some speed test, and this library is slightly (10-20%)
quicker than the library writen in pure PHP.
I haven't compared the API.
Király Péter
http://eXtensibleCatalog.org
2011/1/10 Lukas Kahwe Smith :
>
> On 10.01.2011, at 08:16, Dennis Gearon wrote:
>
>> Anyone have any experience usi
16 matches
Mail list logo
