You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (Commented) (JIRA)" <ji...@apache.org> on 2011/11/28 22:01:40 UTC
[jira] [Commented] (LUCENE-3607) Lucene Index files can not be
reproduced faithfully (due to timestamps embedded)
[ https://issues.apache.org/jira/browse/LUCENE-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158760#comment-13158760 ]
Michael McCandless commented on LUCENE-3607:
--------------------------------------------
This hasn't yet been fixed... when Lucene makes a new index, it sets the "version" field in SegmentInfos to System.currentTimeMillis().
The comment says this:
{noformat}
/**
* counts how often the index has been changed by adding or deleting docs.
* starting with the current time in milliseconds forces to create unique version numbers.
*/
{noformat}
But... I don't see why we need unique version numbers across different indices. I don't think we advertise (nor, should) that the version number you get out of IR is comparable across indices created anew... so I think we can change this to set initial version to 0 instead.
> Lucene Index files can not be reproduced faithfully (due to timestamps embedded)
> --------------------------------------------------------------------------------
>
> Key: LUCENE-3607
> URL: https://issues.apache.org/jira/browse/LUCENE-3607
> Project: Lucene - Java
> Issue Type: Bug
> Components: core/index
> Affects Versions: 2.9.1
> Environment: Eclipse 3.7
> Reporter: Martin Oberhuber
>
> Eclipse 3.7 uses Lucene 2.9.1 for indexing online help content. A pre-generated help index can be shipped together with online content. As per
> [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=364979 ]]
> it turns out that the help index can not be faithfully reproduced during a build, because there are timestamps embedded in the index files, and the "NameCounter" field in segments_2 contains different contents on every build.
> Not being able to faithfully reproduce the index from identical source bits undermines trust in the index (and software delivery) being correct.
> I'm wondering whether this is a known issue and/or has been addressed in a newer Lucene version already ?
--
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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org