Index time and query time boosts have different meanings.
Boosting at index time says "this document's title is more
important than other documents titles". Query time boosts
express "I want matches in the title of a document to count
more than matches in other fields for this query". I guess if
yo
Here is my index structure.
for each document:
Field articleTitle (only one value)
Field majorHeading(multiple values)
Field minorHeading (multiple values)
I use heading (can be both majorHeadings or minorHeadings) to search. What
I want is that majorHeading i
Early Bird Registration for Surge Scalability Conference 2010 ends next
Tuesday, August 31. We have a killer lineup of speakers and architects
from across the Internet. Listen to experts talk about the newest
methods and technologies for scaling your Web presence.
http://omniti.com/surge/2010/re
I'm assuming that the queries you're timing also do not sort. Warmup queries
that don't sort also don't help speed up the first queries that do sort.
But assuming that sorting isn't the problem, you'll need to do a bit of
performance
monitoring. You haven't mentioned what op system you're using, s
Sanne,
I'd prefer to use symlinks for existing, static indexes, but I'm really glad
you showed me FileSwitchDirectory. I think it will be useful for me in the
future. Thanks for your advice!
Any tips on how to convert an existing CFS index to non-CFS? I'm aware of
the extractor in IndexReader, bu
Hi,
I get it working..here is logic that need to implement...
In function getTermQuery check term is stop word or not if it is stop
word then return null.
Otherwise return SrndTermQuery object..
Code ...
protected SrndQuery getTermQuery(
String term, boolean quoted) {
if(stopword
Hi,
I mean to say ..if I want to query like "Solr rocks" with Surround query
then I have to explicitly pass slop like "Solr 1w rocks"
I want to implement this logic in code so user can only enter "solr
rocks"..so internally default operator (1w) will be added inbetween two
words.
Any suggestions
Hi,
Can any one guide me.. how I can accomplish to add default operator
(W/1) in surround query ?
Thanks,
Jagdish
The queries that I have recorded performance for matches documents ranging from
340 to 3000. I am not processing any documents yet; I mean time of 2 seconds
does not include time for processing /collect scoreDocs...
Thanks and Regards,
Shelly Singh
Center For KNowledge Driven Information System
On Fri, 2010-08-27 at 05:34 +0200, Shelly_Singh wrote:
> I have a lucene index of 100 million documents. [...] total index size is
> 7GB.
[...]
> I get a response time of over 2 seconds.
How many documents match such a query and how many of those documents do
you process (i.e. extract a term f
Can you tell us what your queries are? Is it simple term queries,
phrases, fuzzy, etc?
I think the bad guy here is the term "hotel", that so many documents
contains it. You could try loading the full index to II and see how
long time it take to match just that term and compare. And then try
11 matches
Mail list logo
