I need an urgent help.
I want to change the page ranking algorithm in lucene and I do not know
where to start from and what file should I change?
I do not know what classes are involved. I have only a few days to do so, so
please help me with your complete explanation as a big favor!
Bests,
Eric
I need an urgent help.
I want to change the page ranking algorithm in lucene and I do not know
where to start from and what file should I change?
I do not know what classes are involved. I have only a few days to do so, so
please help me with your complete explanation as a big favor!
Bests,
Eric
Dan,
I agree Lucene users are repeatedly solving the same
problems of reading, writing and creating indexes,
building queries, scaling, parsing docs etc.
There's a 'HowTo' section on the Wiki made
for sharing tips and best practices:
http://wiki.apache.org/lucene-java/HowTo
but few new addition
On Friday 13 April 2007 04:04, Erick Erickson wrote:
> As I understand it, there really is no "space indicator". I think of it
> as replacing the stop word with a space, which is then discarded.
You can replace all stop words by your own special term value
to have space indicator.
It is also pos
: Apologies and thanks all at the same time, everyone.
No apologies neccessary, you're not the first person to be confused by
this, which is why I asked if you had any ideas on how we can improve hte
docs -- people who know the APIs inside and out aren't in the best
position to understand how to
"sai hariharan" <[EMAIL PROTECTED]> wrote on 13/04/2007 01:50:35:
> Hi to all,
>
> I've an algortihm thats given below, can anybody help me implementing it.
> Any sort of suggestion will be appreciated. I've finished removing stop
> words,
> calculating term frequencies with Lucene. The rest of th
excluding them completely is a slightly differnet task, you don't need to
index a special marker value, you can just use a
RangeFilter (or ConstantScoreRangeQuery) to ensure you only get docs with
a value for that field (ie: field:[* TO *])
Excellent, this is a much better solution. BTW, adding
Interesting, that does not work for me either. It appears the first test
should expect that the index has doubled in size.
raikoe wrote:
>
> Hello,
>
> i've got the same problem.
> I found a (non-satisfying) solution:
> If I change the variable spellindex to an FSDirectory the TestCase is
>
Hello,
i've got the same problem.
I found a (non-satisfying) solution:
If I change the variable spellindex to an FSDirectory the TestCase is
working.
e.g. spellindex = FSDirectory.getDirectory("d://spellcheckerindex"); instead
of
spellindex = new RAMDirectory();
But I do not understand wh
Apologies and thanks all at the same time, everyone.
Mike
On 4/12/07, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: Michael Barbarelli wrote:
: > Can I instantiate a standard analyzer with an argument containing my
own
: > stop words? If so, how? Will they be appended to or override the
bui
Hi to all,
I've an algortihm thats given below, can anybody help me implementing it.
Any sort of suggestion will be appreciated. I've finished removing stop
words,
calculating term frequencies with Lucene. The rest of the part is not quite
clear.
I'm working only on the English part.
3.2.3 Extra
I'm reading this list eventually but it a very active list and
useful,thks to all.
But so often, when a developer search how to work with lucene finds normally
the same code for same problems.
I think it will be useful create something like Best practices with Lucene
or something similar.
My
12 matches
Mail list logo
