lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 6968] New: - IndexWriter
Date Thu, 07 Mar 2002 22:27:05 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6968>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6968

IndexWriter

           Summary: IndexWriter
           Product: Lucene
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Index
        AssignedTo: lucene-dev@jakarta.apache.org
        ReportedBy: stng@theculprit.com


While the input sources are abstracted, the indices are always files in the 
FileSystem.  It would be nice to abstract the IndexWriter to output to other 
data stores.

For example, I would like to trying to use Lucene to index and search a set of 
short-lived documents while involved in a P2P environment.  Ideally, this 
index (which would be single merge for each peer) can reside in memory rather 
than in the file system (for reasons of security as much as anything else -- 
I'd prefer not to require permission to write out to the user's filesystem).

I think it'd be a nice addition to Lucene.  It would make the Lucene engine 
more easily embedded into other apps.

--
To unsubscribe, e-mail:   <mailto:lucene-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:lucene-dev-help@jakarta.apache.org>


Mime
View raw message