[
https://issues.apache.org/jira/browse/LUCENE-2356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850928#action_12850928
]
Earwin Burrfoot commented on LUCENE-2356:
-----------------------------------------
That's likely orthogonal.
If you want all IW readers to have same divisor - shove it into IWC and it's
all done.
If you want to use different divisors when returning SR as a part of NRT reader
and using it inside (say, for deletions) - okay, you'll have the ability to do
that at the cost of partial SR reload - shove two settings into IWC and it's
done.
> Enable setting the terms index divisor used by IndexWriter whenever it opens
> internal readers
> ---------------------------------------------------------------------------------------------
>
> Key: LUCENE-2356
> URL: https://issues.apache.org/jira/browse/LUCENE-2356
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Michael McCandless
> Fix For: 3.1
>
>
> Opening a place holder issue... if all the refactoring being discussed don't
> make this possible, then we should add a setting to IWC to do so.
> Apps with very large numbers of unique terms must set the terms index divisor
> to control RAM usage.
> (NOTE: flex's RAM terms dict index RAM usage is more efficient, so this will
> help such apps).
> But, when IW resolves deletes internally it always uses default 1 terms index
> divisor, and the app cannot change that. Though one workaround is to call
> getReader(termInfosIndexDivisor) which will pool the reader with the right
> divisor.
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
