[
https://issues.apache.org/jira/browse/LUCENE-2446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955173#comment-13955173
]
Robert Muir commented on LUCENE-2446:
-------------------------------------
You guys figure out the name for the method, i really dont care. I will wait on
the issue until you guys bikeshed it out. The only thing i care about is that
its not mixed up with other logic.
Its really important when debugging a corrupt index that you can know that the
file itself is corrupted (e.g. hardware) versus some bug in lucene. Its also
really important that there is at least the option (like there is in this
patch) to prevent this corruption from being propagated in merge. So lets
please not mix unrelated stuff in here.
Things like refactoring checkindex or whatever: please just open a separate
issue for that :)
> Add checksums to Lucene segment files
> -------------------------------------
>
> Key: LUCENE-2446
> URL: https://issues.apache.org/jira/browse/LUCENE-2446
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: Lance Norskog
> Labels: checksum
> Attachments: LUCENE-2446.patch
>
>
> It would be useful for the different files in a Lucene index to include
> checksums. This would make it easy to spot corruption while copying index
> files around; the various cloud efforts assume many more data-copying
> operations than older single-index implementations.
> This feature might be much easier to implement if all index files are created
> in a sequential fashion. This issue therefore depends on [LUCENE-2373].
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
