lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Jakarta Lucene Wiki] Updated: Lucene2Whiteboard
Date Wed, 08 Sep 2004 10:07:31 GMT
   Date: 2004-09-08T03:07:31
   Editor: DanielNaber <>
   Wiki: Jakarta Lucene Wiki
   Page: Lucene2Whiteboard

   no comment

Change Log:

@@ -30,6 +30,8 @@
  11. (Hard) Make indexing more flexible, so that one could e.g., not store positions or even
frequencies, or alternately, to store extra information with each position, or to even use
different posting compression algorithms.  This could be implemented by extending Field to
specify a FieldIndexer.  A FieldIndexer would be passed each token and decide what about it
to record, how to record it, etc.  All fields with the same name must use the same FieldIndexer
implementation.  The FieldIndexer implementation would be serialized with the index.  Detailed
specification of a FieldIndexer API is required before this proposal can be seriously considered.
+ 12. Modify MultiFieldQueryParser so that it behaves as most people expect: searching for
A AND B in the fields body, title means that both terms must occur, but it doesn't matter
whether they occur in title or body. The old behaviour must still be available by default
so we stay compatible.
 == Other Changes ==
 Here's a list of planned changes that either don't affect the API or that can be implemented
in an API compatible way:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message