[
https://issues.apache.org/jira/browse/LUCENE-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13912384#comment-13912384
]
Hoss Man commented on LUCENE-5472:
----------------------------------
bq. nor have i run any other tests to see if throwing an exception here breaks
any other existing tests that happen to depend on big ass terms being silently
ignored.
no surprises jumped out at me when running all tests, although there was an
un-surprising failure from TestIndexWriter.testWickedLongTerm which asserts the
exact opposite of the new test i added here: that a doc with a "wicket long"
term can still be added.
Assuming people think the overall change should happen, removing/fixing that
test would be trivial.
> Long terms should generate a RuntimeException, not just infoStream
> ------------------------------------------------------------------
>
> Key: LUCENE-5472
> URL: https://issues.apache.org/jira/browse/LUCENE-5472
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Hoss Man
> Attachments: LUCENE-5472.patch
>
>
> As reported on the solr-user list, when a term is greater then 2^15 bytes it
> is silently ignored at indexing time -- a message is logged in to infoStream
> if enabled, but no error is thrown.
> seems like we should change this behavior (if nothing else starting in 5.0)
> to throw an exception.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
