[
https://issues.apache.org/jira/browse/LUCENE-5472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13913557#comment-13913557
]
Hoss Man commented on LUCENE-5472:
----------------------------------
bq. I tweaked the patch a bit
Looks pretty good, although "maxTermField" in DocumentsWriterPerThread looks
like a new unused variable ... cruft from a different approach you were going
to take?
Do you think this should be committed only to trunk, or trunk & 4x - or is it
too much of a runtime behavior change to put on 4x?
Can/should we make throwing an exception dependent on the Version used in the
IndexWriterConfig? (it's not clear to me if enough IW context is passed down to
DocInverterPerField currently to even access the Version)
> 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, 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]
