[
https://issues.apache.org/jira/browse/LUCENE-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12987124#action_12987124
]
Robert Muir commented on LUCENE-2891:
-------------------------------------
bq. -1 means "don't load terms index because I will never, ever seek-by-Term".
As far as I know, it's only segment merging that does this...
but it allows next()'ing through all the terms only?
I suggested the testing because I had seen some code for -1 but I didn't know
how tested it is,
its a tad confusing in the javadoc which just says "Set this to -1 to skip
loading the terms index entirely."
This makes me think (based on the language "skip loading"), that if you do this
everything will still work,
but seek() will just be brute-force or something aweful...
> IndexWriterConfig does not allow termInfosDivisor to be -1, while the latest
> indicates TermInfos should not be loaded
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2891
> URL: https://issues.apache.org/jira/browse/LUCENE-2891
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Reporter: Shai Erera
> Assignee: Shai Erera
> Fix For: 3.1, 4.0
>
> Attachments: LUCENE-2891.patch, LUCENE-2891.patch
>
>
> While you can pass -1 to IR.open(), and it's documented, you cannot do the
> same for IndexWriter's readers (b/c IWC blocks it). Need to allow this
> setting as well as add support for it in our tests, e.g. we should randomly
> set it to -1. Robert also suggested RandomIW use -1 randomly when it opens
> readers.
> I'll work on a patch
--
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: [email protected]
For additional commands, e-mail: [email protected]
