[
https://issues.apache.org/jira/browse/SOLR-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976180#comment-13976180
]
Erick Erickson commented on SOLR-5999:
--------------------------------------
The @Test is the Junit4 way of doing things though, figuring out that it's a
test due to the naming convention is the Junit3 way. Currently a matter of
preference I admit...
> Solr should expose setCheckIntegrityAtMerge in indexConfig
> ----------------------------------------------------------
>
> Key: SOLR-5999
> URL: https://issues.apache.org/jira/browse/SOLR-5999
> Project: Solr
> Issue Type: New Feature
> Reporter: Varun Thacker
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-5999.patch
>
>
> LUCENE-2446 added checksums to Lucene segment files. We could expose
> CheckIntegrityAtMerge in the indexConfig tag in solrconfig.xml.
> Something like -
> {noformat}
> <!--
> Use true to enable this safety check, which can help
> reduce the risk of propagating index corruption from older
> segments
> into new ones, at the expense of slower merging.
> -->
> <checkIntegrityAtMerge>false</checkIntegrityAtMerge>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
