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

[mbjones]

---

Author Name: Jing Tao (Jing Tao) Original Redmine Issue: 6306, https://projects.ecoinformatics.org/ecoinfo/issues/6306 Original Date: 2013-12-16 Original Assignee: Jing Tao

---

If the index schema was modified, users shouldn't see the message.

[mbjones]

---

Original Redmine Comment Author Name: Jing Tao (Jing Tao) Original Date: 2013-12-16T22:07:22Z

---

The version of the previous metacat is 2.2.1

[mbjones]

---

Original Redmine Comment Author Name: Jing Tao (Jing Tao) Original Date: 2013-12-18T01:35:40Z

---

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.

[mbjones]

---

Original Redmine Comment Author Name: ben leinfelder (ben leinfelder) Original Date: 2014-01-31T22:48:20Z

---

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.

[mbjones]

---

Original Redmine Comment Author Name: ben leinfelder (ben leinfelder) Original Date: 2014-02-13T20:04:52Z

---

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.

[mbjones]

---

Original Redmine Comment Author Name: ben leinfelder (ben leinfelder) Original Date: 2014-02-14T19:15:22Z

---

Not really sure what was happening, but not really able to replicate reliably.

[mbjones]

Closing because 2.3.0 has now been deprecated.