You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucy.apache.org by "Marvin Humphrey (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/27 03:16:40 UTC
[lucy-issues] [jira] [Resolved] (LUCY-193) Occasional schema file name collision
under 'truncate'
[ https://issues.apache.org/jira/browse/LUCY-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marvin Humphrey resolved LUCY-193.
----------------------------------
Resolution: Fixed
> Occasional schema file name collision under 'truncate'
> ------------------------------------------------------
>
> Key: LUCY-193
> URL: https://issues.apache.org/jira/browse/LUCY-193
> Project: Lucy
> Issue Type: Bug
> Components: Index
> Affects Versions: 0.1.0 (incubating), 0.2.0 (incubating), 0.2.1 (incubating), 0.2.2 (incubating)
> Reporter: Marvin Humphrey
> Assignee: Marvin Humphrey
> Priority: Minor
> Fix For: 0.3.0 (incubating)
>
>
> When 'truncate' is true for an Indexer's constructor, by a
> quirk of fate, it will always write a schema file named
> "schema_1.json". If the existing schema file is also named that
> (as it would be on successive truncating runs), the files will
> collide, resulting in either a clobber a crash depending on OS.
> The solution is to derive the name of the schema file from the
> name of the snapshot file.
> Original user list trouble report: http://s.apache.org/90L
--
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