DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=36623>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=36623 Summary: RAMInputStream without further buffering Product: Lucene Version: CVS Nightly - Specify date in submission Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: Store AssignedTo: java-dev@lucene.apache.org ReportedBy: [EMAIL PROTECTED] >From java-dev, Doug's reply of 12 Sep 2005 on Delaying buffer allocation in BufferedIndexInput: Paul Elschot wrote: ... > I noticed that RAMIndexInput extends BufferedIndexInput. > It has all data in buffers already, so why is there another > layer of buffering? No good reason: it's historical. To avoid this either: (a) the BufferedIndexInput API would need to be modified to permit subclasses to supply the buffer; or (b) RAMInputStream could subclass IndexInput directly, using its own buffers. The latter would probably be simpler. End of quote. I made version (b) of RAMInputStream. Using this RAMInputStream, TestTermVectorsReader failed as the only failing test. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
