:-) I changed the main lines and compiled the QueryParser.java after that I
compiled the entire package, build a new jar file and installed it on my
server. (I followed the same procedure I used when I added a new analyzer)
Cheers
Chris
-Original Message-
From: Erik Hatcher [mailto:[EMAI
I was following an example in a book that referenced that taglib :) Book's
copyrighted 2004 so there may be at least a small user base out there. I
finally got the Sandbox version to work correctly on lucene 1.2. It doesn't
work on 1.4.x.
Perhaps it may be an overkill of a taglib, but my fami
Chris,
Once upon a time there was a taglib area in the Lucene Sandbox, but
that has since been removed since the contributor of it disappeared.
What do you need a Lucene taglib to do? I personally thing such a
taglib is overkill and harder to use than it would be to just code up
the func
Hello,
Looking for most useful lucene taglib and have found references to one written
by a Iskandar Salim found at www.javaxp.net/lucene-taglib, but that site is
404. Found a patch submited in 2003 bug# 20283. Downloaded and seems adequate,
but from the docs I've read, the javaxp seems superio
Well, I guess Lucene's Span query uses the Cover Density based model
(proximity model). However, it is within the framework of the TF*IDF
as well.
Jian
On 7/4/05, Dave Kor <[EMAIL PROTECTED]> wrote:
> Quoting [EMAIL PROTECTED]:
>
> > Hi everybody,
> >
> > which kind of retrieval model is lucene
A couple of sanity checks... you changes the main lines, not the
comments I hope :) And also, you need to rebuild the parser code by
running JavaCC on it. If you're tinkering with a copy of Lucene's
source code you can run the Ant target "javacc" and you must have
JavaCC installed per the
Hi -
I tried increasing SUMMARY_LENGTH to 1 (originally 200) in HTMLParser.java
and HTMLParser.jj files. The purpose is to create snippet and highlight the
search terms within it.
Then I used ant to compile (also used javacc-HTMLParser, compile, jar,
jar-demo, war-demo and copied war file
Hello,
As i also encountered the phrase query issue with the old highlighter
code, I added a fieldName argument in case of the analyser handle it in the
tokenStream() method.
I just submitted the patch on bugzilla
--- sven
jeudi 30 juin 2005, 22:12:51, vous avez écrit:
BD> FYI, I made an updat
I have found in the QueryParser.jj those lines of comments:
// OG: to support prefix queries:
// http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12137
// Change from:
// |
// (<_TERM_CHAR> | ( [ "*", "?" ] ))* >
// To:
//
// | | ( [ "*", "?" ] ))* >
So as indicated I changed my l
On Jul 4, 2005, at 9:02 AM, BOUDOT Christian wrote:
Hi,
I modified the analyzer (it is now vegetarian and won't eat numbers
anymore
:-) but I have hit a new problem. The parser won't accept a keyword
to start
with a wildcard character. (*/12/2003) Any hints to solve this new
issue?
Thi
Hi,
I modified the analyzer (it is now vegetarian and won't eat numbers anymore
:-) but I have hit a new problem. The parser won't accept a keyword to start
with a wildcard character. (*/12/2003) Any hints to solve this new issue?
Many thanks
Chris
-Original Message-
From: Erik Hatcher
Quoting [EMAIL PROTECTED]:
> Hi everybody,
>
> which kind of retrieval model is lucene using? Is it a simple vector model,
> a extended boolean model or another model? A reliable source with
> information about it would be fine, cause every source i found is telling
> something different. :)
>
Lu
Hi everybody,
which kind of retrieval model is lucene using? Is it a simple vector model,
a extended boolean model or another model? A reliable source with
information about it would be fine, cause every source i found is telling
something different. :)
Greets
Michael
--
Weitersagen: GMX DSL-F
13 matches
Mail list logo
