Bug #6306
closed
During the upgrading metacat to 2.3.0, a user can see a message saying the index schema was changed even though he didn't
Added by Jing Tao over 10 years ago.
Updated about 10 years ago.
Description
If the index schema was modified, users shouldn't see the message.
The version of the previous metacat is 2.2.1
This bug it is harder than I thought because i can reproduce the bug once, then i can't.
I downloaded metacat-bin-2.2.1 and installed it. Then i downloaded metacat-bin-2.3.0 and upgrade it. I got the same message even though i didn't change the schema. I tried to upgrade the metacat from trunk, i didn't see the message. I tried to upgrade from metacat-src-2.3.0 and couldn't see the message. Finally, i tried metacat-bin-2.3.0 again, still couldn't see the message. I will test more on tomorrow.
Reminder: for 2.4.0, I changed the schema.xml to use a copy from the metacat-index project. I need to add this hash to the list of "known" schema versions.
- Status changed from New to In Progress
I included the md5 for the latest version of the schema we are shipping (customized in metacat-common).
Sounds like it is still a mystery about when/why the warning message appears for some users.
- Status changed from In Progress to Works For Me
Not really sure what was happening, but not really able to replicate reliably.
Also available in: Atom
PDF