Make "ant -projecthelp" show the javadocs and docs targets as well
--
Key: LUCENE-447
URL: http://issues.apache.org/jira/browse/LUCENE-447
Project: Lucene - Java
Type: Improvement
Components: Other
[ http://issues.apache.org/jira/browse/LUCENE-447?page=all ]
Luc Vanlerberghe updated LUCENE-447:
Attachment: build.diff
attached diff.
> Make "ant -projecthelp" show the javadocs and docs targets as well
> --
[ http://issues.apache.org/jira/browse/LUCENE-446?page=all ]
Yonik Seeley updated LUCENE-446:
Attachment: ReciprocalFloatFunction.java
ReverseOrdFieldSource.java
Added ReciprocalFloatFunction, a/(mx+b), a natural choice for date boosting,
[ http://issues.apache.org/jira/browse/LUCENE-95?page=all ]
Grant Ingersoll updated LUCENE-95:
--
Attachment: queryTermPositionVector.patch.tar.gz
Attached is an implementation of TermPositionVector for queries. It simply
extends QueryTermVector and pro
Yonik and I have been looking at the memory requirements of an application
we've got. We use a lot of indexed fields, primarily so I can do a lot
of numeric tests (using RangeFilter). When I say "a lot" I mean
arround 8,000 -- many of which are not used by all documents in the index.
Now there
Hi, Chris,
Turning off norm looks like a very interesting problem to me. I remember
that in Lucene Road Map for 2.0, there is a requirement to turn off indexing
for some information, such as proximity.
Maybe optionally turning off the norm could be an experiment to show case
how to turn off the p
: 2) Can you think of a clean way for individual applications to eliminate
: norms (via subclassing the lucene code base - ie: no patching)
For completeness, I should mention that one thing I briefly considered was
writing a new Directory implimentation that would proxy to FSDirectory,
but
I did exactly this in my custom lucene, since the array of a byte per
document is extremely wasteful in a lot of applications. I just changed the
code to return null from getNorms() and modified the callers to treat a null
array as always 1 for any document.
-Original Message-
From: Chris
I'm approaching it the same as term vectors... make the norms optional on a
per field basis.
My first cut is returning a dummy norm array filled in with the equiv of
1.0f so I didn't have to go modify all the queries/weights/scorers that
retrieve the norms. For best performance, those scorers shoul
