Hello,
I need an Analyzer which doesn't separate the
underscored words and with the StandardAnalyzer
functionnalities.
So, the solution is to create a new Analyzer .
I have seen several mails about that. I tried to apply
the proposed solutions but I have a problem.
The idea is to compile from so
On Saturday 25 November 2006 07:59, Otis Gospodnetic wrote:
> Hi,
>
> Poking around Query/Weight/Scorer classes I finally started understanding
how some portions of the scoring works (imagine a lot of lightbulbs now). In
one of my Lucene use-cases I really just use it to pull N documents from a
Simon Willnauer wrote:
I'm actually looking for alternatives and suggestions about this
topic, I know you guys have your own schedule but I would really
appreciate some help with that.
Perhaps the derby would be appropriate,
http://db.apache.org/derby/
It is fairly fast, somewhat scalable
On 11/25/06, Paul Elschot <[EMAIL PROTECTED]> wrote:
On Saturday 25 November 2006 07:59, Otis Gospodnetic wrote:
> Hi,
>
> Poking around Query/Weight/Scorer classes I finally started understanding
how some portions of the scoring works (imagine a lot of lightbulbs now). In
one of my Lucene use-c
[ http://issues.apache.org/jira/browse/LUCENE-721?page=all ]
Michael Busch updated LUCENE-721:
-
Attachment: clover.patch
Here it is, Grant. This new patch uses Clover to generate code coverage
reports. Simply add clover.jar to the ant classpath, do a "c
[ http://issues.apache.org/jira/browse/LUCENE-669?page=all ]
Michael Busch updated LUCENE-669:
-
Attachment: FSDirectory_close_file2.patch
Since the new testcase TestStressIndexing has been added as part of the
lockless commits I see this test failing re
[ http://issues.apache.org/jira/browse/LUCENE-669?page=all ]
Michael Busch updated LUCENE-669:
-
Attachment: (was: FSDirectory_close_file_patch.patch)
> finalize()-methods of FSDirectory.FSIndexInput and FSDirectory.FSIndexOutput
> try to close alrea
