Hi lan
thanks for your reply.
when i boosting each term while searching like abcd is boost with boost
factor of 10 and pqrst boost with boost factor of 5.
then also it gives same score for documents
*Query content:abcd^10.0 content:pqrst^5.0*
title ->pqrst uvwx abcd ::: content -> pqrst uvwx
Hi,
I don't want to filter certain stop words within the StandardAnalyzer? Can
I do so?
Ideally, I would like to have a customized StandardAnalyzer.
Thanks.
Thanks for the reply,
> > The first time my code used the 3.4 libraries with version level set
> > to 3.4 and it tried
> > to optimize() (still using this now deprecated old call), the new code
> went wild!
> > It took up more memory than the heap was limited to, so I believe it
> > is taking
> >
Hi,
> After reading all about the renaming of optimize() and updating my Lucene
> libraries to 3.4, I was surprised and confused by what I found.
>
> I have a 1 segment index (all files are named _1*.*) that had been
created
> with 3.0.1 code which had been optimized many times (all 3.0.1 code)
After reading all about the renaming of optimize() and updating my Lucene
libraries to 3.4, I was surprised and confused by what I found.
I have a 1 segment index (all files are named _1*.*) that had been created
with 3.0.1 code which had been optimized many times (all 3.0.1 code). The
first
On Fri, Jan 27, 2012 at 4:53 PM, Hany Azzam wrote:
> Hi Robert,
>
> Thanks for the reply. I am trying to do something different. If I use a
> mutireader then the searching/scoring will take place over the two indexes at
> the same time. However, in my case the subcomponents of the retrieval mode
Hi Robert,
Thanks for the reply. I am trying to do something different. If I use a
mutireader then the searching/scoring will take place over the two indexes at
the same time. However, in my case the subcomponents of the retrieval model are
calculated over separate evidence spaces. For example,
On Fri, Jan 27, 2012 at 3:21 PM, Hany Azzam wrote:
> Hi,
>
> I have two indexes. One that contains all the documents in the collection and
> the other contains only the relevant documents. I am using Lucene 4.0 and the
> new SimilariyBase class to build my retrieval models (similarity functions)
Hi,
I have two indexes. One that contains all the documents in the collection and
the other contains only the relevant documents. I am using Lucene 4.0 and the
new SimilariyBase class to build my retrieval models (similarity functions).
One of the retrieval models requires statistics to be comp
One addition:
In general, your way how to get a scorer from a query is not supported (and
does not work correct for all queries), the right way is *not* to use
query.createWeight(searcher) but instead
searcher.createNormalizedWeight(query).
But that has nothing to do with the null scorer, which i
You are creating a TermScorer on a composite (non atomic IndexReader like
SegmentReader). That's still supported in 3.x, but no longer allowed in 4.0.
The backwards layer in 3.x had a bug before Lucene 3.5, so theoretically
your code should work on 3.5:
https://issues.apache.org/jira/browse/LUCENE-
On 10/01/2012 12:26, Paul Taylor wrote:
On 10/01/2012 10:18, Ian Lea wrote:
If a term has an accent, add both accented and unaccented versions at
index and search time.
So in your example your default field would contain
República Republica
and a search for "República" would expand to "Repúbl
Hi!
I have a Solr-constructed index, which I read with this code:
Directory directory = FSDirectory.open(file);
IndexReader reader = IndexReader.open(directory, true);
IndexSearcher searcher = new IndexSearcher(reader);
I try to get a Scorer with this TermQuery ("lang" field is indexed
and stor
13 matches
Mail list logo
