[LUCENE-431] RAMInputStream and RAMOutputStream without further buffering

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Component/s: core/store

Environment

Operating System: other
Platform: Other

• Lucene Fields: Patch Available
• Bugzilla Id: 36623
• Assignee: Michael Busch
• Reporter: Paul Elschot
• Created: 13/Sep/05 04:08
• Updated: 28/Aug/22 11:23
• Resolved: 17/Apr/07 20:13

Description

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.