[
https://issues.apache.org/jira/browse/LUCENE-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir resolved LUCENE-3874.
---------------------------------
Resolution: Fixed
The solution here is 100% correct, we don't need to reopen it because its test
found a separate, unrelated bug.
any shit that limits your values to smaller than integer.max_value needs its
own checks to fit, throwing UOE because its choosing not to support totally
legitimate values from the analyzer.
> bogus positions create a corrumpt index
> ---------------------------------------
>
> Key: LUCENE-3874
> URL: https://issues.apache.org/jira/browse/LUCENE-3874
> Project: Lucene - Java
> Issue Type: Bug
> Affects Versions: 3.6, 4.0
> Reporter: Robert Muir
> Fix For: 3.6, 4.0
>
> Attachments: LUCENE-3874.patch, LUCENE-3874_test.patch
>
>
> Its pretty common that positionIncrement can overflow, this happens really
> easily
> if people write analyzers that don't clearAttributes().
> It used to be the case that if this happened (and perhaps still is in 3.x, i
> didnt check),
> that IW would throw an exception.
> But i couldnt find the code checking this, I wrote a test and it makes a
> corrumpt index...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
