Bug 32107 - Index signature change isn't honoured any longer
Summary: Index signature change isn't honoured any longer
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P2 critical (vote)
Target Milestone: 2.1 RC1   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-18 07:22 EST by Philipe Mulet CLA
Modified: 2003-03-11 07:37 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2003-02-18 07:22:52 EST 
Build 20030214

When an index signature is changed, the index manager will not force it to be 
recreated if it thinks it can be trusted.

Offending code seems to be:
IndexManager#getIndex(...) which only looks at the state of the index, and 
ignore its signature.

When opening the corresponding index, later on, it is too late, an IO Exception 
is thrown, but it doesn't end up recreating the index, simply failing the 
search action (no match).

Must fix for 2.1
Comment 1 Philipe Mulet CLA 2003-02-18 07:40:15 EST 
Added a check on IndexManager#getIndex, when about to reuse existing file.
Fixed.
Comment 2 Kent Johnson CLA 2003-02-18 15:28:41 EST 
Replaced the fix. The problem was actually in Index.initialize().

If the index was incompatible, it was being deleted & replaced with an empty 
index.
Comment 3 David Audel CLA 2003-03-11 07:37:01 EST 
Verified.