Re: Eliminating norms ... completley

2005-10-08 Thread Paul Elschot
On Friday 07 October 2005 23:18, Chris Hostetter wrote: > ... > So I'm curious what you guys think... > > 1) Regarding the root problem: is there any other things you can think > of besides norms[] that would contribute to the memory foot print > needed by a large number of indexed f

[jira] Resolved: (LUCENE-447) Make "ant -projecthelp" show the javadocs and docs targets as well

2005-10-08 Thread Daniel Naber (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-447?page=all ] Daniel Naber resolved LUCENE-447: - Fix Version: 1.9 Resolution: Fixed Thanks, the patch has juts been committed. > Make "ant -projecthelp" show the javadocs and docs targets as well

[jira] Updated: (LUCENE-395) CoordConstrainedBooleanQuery + QueryParser support

2005-10-08 Thread paul.elschot (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-395?page=all ] paul.elschot updated LUCENE-395: Attachment: TestBooleanMinShouldMatch.java Some refactoring to make things more compact, no functional changes. > CoordConstrainedBooleanQuery + QueryParser su

[jira] Created: (LUCENE-448) optional norms

2005-10-08 Thread Yonik Seeley (JIRA)
optional norms -- Key: LUCENE-448 URL: http://issues.apache.org/jira/browse/LUCENE-448 Project: Lucene - Java Type: New Feature Components: Index Versions: CVS Nightly - Specify date in submission Reporter: Yonik Seeley Attachments: omitN

[jira] Updated: (LUCENE-448) optional norms

2005-10-08 Thread Yonik Seeley (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-448?page=all ] Yonik Seeley updated LUCENE-448: Attachment: omitNorms.txt > optional norms > -- > > Key: LUCENE-448 > URL: http://issues.apache.org/jira/browse/LUCENE-448 >

[jira] Updated: (LUCENE-395) CoordConstrainedBooleanQuery + QueryParser support

2005-10-08 Thread paul.elschot (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-395?page=all ] paul.elschot updated LUCENE-395: Attachment: BooleanScorer2.java This a continuation of the earlier patch. The basic ideas are now built deep into the logic of determining the actual scorer to

Re: Eliminating norms ... completley

2005-10-08 Thread Yonik Seeley
Here's my patch for the indexing and IndexReader side of things. Works like a charm. http://issues.apache.org/jira/browse/LUCENE-448 This doesn't yet include performance enhancements to scorers when norms aren't included, but I first wanted to make sure things were completely backward compatible

[jira] Commented: (LUCENE-364) Further improvements to BooleanScorer2

2005-10-08 Thread paul.elschot (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-364?page=comments#action_12331655 ] paul.elschot commented on LUCENE-364: - The code posted here is obsoleted by the BooleanScorer2 posted at issue LUCENE-395 . The optimization here is currently not included

[jira] Commented: (LUCENE-395) CoordConstrainedBooleanQuery + QueryParser support

2005-10-08 Thread paul.elschot (JIRA)
[ http://issues.apache.org/jira/browse/LUCENE-395?page=comments#action_12331656 ] paul.elschot commented on LUCENE-395: - The code that is obsoleted by this BooleanScorer2 is at issue LUCENE-364. > CoordConstrainedBooleanQuery + QueryParser support > ---

Adding information to an index

2005-10-08 Thread Anton Leuski
Greetings, I'm looking to store some additional information in a Lucene index and I'm looking for an advise on how to implement the functionality. Specifically, I'm planning to store 1) collection frequency count for each term, 2) actual document length for each document (yes, I looked at