Dear List,
I'm running a prefix query, something like this: text:dummy*. The problem:
in the result some non-exact matches get higher scores than the exact ones.
For example the document containing dummythales comes before the document
containing dummy exactly. How can this behavious be changed?
A common practice is to search for an exact match, boosted, as well as
a wildcard match e.g.
text:dummy^4 text:dummy*
http://lucene.apache.org/java/3_3_0/queryparsersyntax.html#Boosting%20a%20Term
http://wiki.apache.org/lucene-java/LuceneFAQ#What_is_the_difference_between_field_.28or_document.29_
Thanks yor your answer!
Tajti Ákos
On Tue, Sep 6, 2011 at 11:34 AM, Ian Lea wrote:
> A common practice is to search for an exact match, boosted, as well as
> a wildcard match e.g.
>
> text:dummy^4 text:dummy*
>
>
> http://lucene.apache.org/java/3_3_0/queryparsersyntax.html#Boosting%20a%20Term
Closing a searcher while thread(s) is/are still using it is definitely
bad, so, this code looks spooky...
But: it possible something higher up (in Solr) is ensuring this code
runs exclusively? I don't know enough about this part of Solr...
Mike McCandless
http://blog.mikemccandless.com
On Mon,
Hi All,
I have a question about index size growing exponentially as the index goes
larger.
I am indexing last 2 years worth of data. Initially the index was growing 5
GB for every 1 month. At the end of the 4th month of indexing my index size
was 20GB (I was watching index size every few minutes)
: You can use IndexReader's setNorm method?
:
: It's an expert method, and accepts a new byte norm value for the doc X
: field, ie you'll have to compute the right byte value.
In particular, you should take a look at the FieldNormModifier utility.
It was created for the purpose of trying out d
You can try an optimize on the index, but if you haven't deleted (or updated)
any docs I wouldn't actually expect that to help much.
A reasonable question is what's actually in your index. This page will
tell you what sorts of data are in what extensions:
http://lucene.apache.org/java/3_0_2/filefo
Thank you very much!
Tajti Ákos
On 2011.09.06., at 18:42, Chris Hostetter wrote:
>
> : You can use IndexReader's setNorm method?
> :
> : It's an expert method, and accepts a new byte norm value for the doc X
> : field, ie you'll have to compute the right byte value.
>
> In particular, you sh
Hi,
I am facing a error while processing a set of data.. the description says
"Failed to create text index reader for .../.../_166.frq (The System cannot
find the specified path).
I have never seen this error in the past neither have I seen this file in
the index folder ever. Does lucene take ca
Hmmm, it rather looks like somehow some of your
index files got deleted from your index directory.
a .frq file is one of the files that contains document
frequency information. The fact that Lucene
can't find _166.frq indicates you've been using this
index for a while and created a bunch of segment
hi:
We want to use lucene in our website,The team is confued with using which
version in our project.I google a lot and see the changelog on apache site.But
i did not get a lot more usefule info.I personally want to use the latest
verion of lucene.But i can not persuade the team.Could anyone
11 matches
Mail list logo