[
https://issues.apache.org/jira/browse/LUCENE-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2453:
------------------------------------
Affects Version/s: (was: 3.0.1)
4.0
4.1
Fix Version/s: 5.0
4.2
> Make Index Output Buffer Size Configurable
> ------------------------------------------
>
> Key: LUCENE-2453
> URL: https://issues.apache.org/jira/browse/LUCENE-2453
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/store
> Affects Versions: 4.0, 4.1
> Reporter: Karthick Sankarachary
> Assignee: Simon Willnauer
> Fix For: 4.2, 5.0
>
> Attachments: LUCENE-2453.patch, LUCENE-2453.patch
>
>
> Currently, the buffered index input class allows sub-classes and users
> thereof to specify a size for the input buffer, which by default is 1024
> bytes. In practice, this option is leveraged by the simple file and compound
> segment index input sub-classes.
> By the same token, it would be nice if the buffered index output class could
> open up it's buffer size for users to configure. In particular, this would
> allow sub-classes thereof to align the output buffer size, which by default
> is 16348 bytes, to that of the underlying directory's data unit. For example,
> a network-based directory might want to buffer data in multiples of it's
> maximum transmission unit. To use an existing use-case, the file system-based
> directory could potentially choose to align it's output buffer size to the
> operating system's file block size.
> The proposed change to the buffered index output class involves defining a
> one-arg constructor that takes a user-defined buffer size, and a default
> constructor that uses the currently defined buffer size.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
