jira at apache
Apr 17, 2007, 1:13 PM
Post #1 of 1
(227 views)
Permalink
|
|
[jira] Resolved: (LUCENE-431) RAMInputStream and RAMOutputStream without further buffering
|
|
[ https://issues.apache.org/jira/browse/LUCENE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Busch resolved LUCENE-431.
----------------------------------
Resolution: Fixed
Thanks for the quick (7 mins!) response, Mike :-).
I just committed it.
> RAMInputStream and RAMOutputStream without further buffering
> ------------------------------------------------------------
>
> Key: LUCENE-431
> URL: https://issues.apache.org/jira/browse/LUCENE-431
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Store
> Affects Versions: CVS Nightly - Specify date in submission
> Environment: Operating System: other
> Platform: Other
> Reporter: Paul Elschot
> Assigned To: Michael Busch
> Priority: Minor
> Attachments: lucene-431.patch, lucene-431.zip, RAMInputStream.java
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe [at] lucene
For additional commands, e-mail: java-dev-help [at] lucene
|
