Re: Upgrade eXist-db from 2.1 to 6.2.0

Thank you all for the excellent advice. Last week I upgraded to 6.2, and most of our queries are working correctly except for minor changes. I notice some issues with the indexing; I will look into this in detail.
Thank you again for your suggestion and recommendation.
--
Alem T. Areki
Senior Web Developer – Web Services
University of Richmond

From: Alexander Henket <[email protected]>
Date: Saturday, February 11, 2023 at 1:57 AM
To: "[email protected]" <[email protected]>
Subject: Re: [Exist-open] Upgrade eXist-db from 2.1 to 6.2.0

External Email: Use caution in opening links, attachments, and buying gift cards.

All advice from Pieter. Additionally assess your index strategy. The index definitions from 2.1 will work, or at least ours from 2.2 did, but upgrading from old range to new range or more sophisticated methods are worth inspecting.

Also from our perspective: backup/restore is a good start but that works best for data/users not so much for logic/applications. So if you like us have a mix of data and apps in 2.1 you might want to tweak the backup zip so it only contains data and users. Do the applications using xar install.

Xar install might fail until pre/post-install scripts are updated for xquery 3.1. Exist-db 2 used preliminary syntax for xquery 3.0/1 which exist-db >= 5 no longer supports like Pieter mentioned:

eXist-db Documentation<https://exist-db.org/exist/apps/doc/upgrading>
exist-db.org<https://exist-db.org/exist/apps/doc/upgrading>
[exist_icon_16x16.ico]<https://exist-db.org/exist/apps/doc/upgrading>

Most code issues you’ll have started with exist-db 5. The release notes outline what they are and link to the perl script

Atomic Wiki<http://www.exist-db.org/exist/apps/wiki/blogs/eXist/eXistdb500>
exist-db.org<http://www.exist-db.org/exist/apps/wiki/blogs/eXist/eXistdb500>
[exist_icon_16x16.ico]<http://www.exist-db.org/exist/apps/wiki/blogs/eXist/eXistdb500>

Everything mentioned there still holds true in exist-db 6.

It took us over a year to update the code, rethink index, rethink code security, test and finally migrate. For UI we had Orbeon xforms inside the db that we replace with a Roaster/jwt based api and external Vue based logic. Roaster and jwt are in the public repo and work with >= 5 and up. The orbeon to vue move is now 3 years in the making. They still run side by side. We found the best start in Roaster by hiring eXist people. The rest we could largely manage ourselves.

Verstuurd vanaf mijn iPhone


Op 11 feb. 2023 om 07:14 heeft Pieter Lamers <[email protected]> het volgende geschreven:

I would not follow this advice. Any new release can be indefinitely delayed, and I suspect that even with the promise of some breaking changes between 6.2 and 7 there will be much more common ground between those than between 2.1 and 6.2.

I would start by installing 6.2 locally and see if I can restore a backup onto it. Then see where the code breaks. There is a perl (!) script out there which can trace some now invalid constructs, like maps with key := val instead of  key : val. There is a lot of code refactoring possible now: eXist 6.2 uses a recent version of Saxon which supports text value templates (and XSLT 3.0 in general). eXist's XQuery has a much broader coverage of the 3.1 standard.

Probably some other community members have a more sophisticated approach, so let's see what the others say.

Best,
Pieter
On 07/02/2023 06:44, Martin Mueller wrote:
You might as well wait until the promised version 7 comes out in the spring.

From: "Areki, Alem" <[email protected]><mailto:[email protected]>
Date: Monday, February 6, 2023 at 8:23 PM
To: "[email protected]"<mailto:[email protected]> <[email protected]><mailto:[email protected]>
Subject: [Exist-open] Upgrade eXist-db from 2.1 to 6.2.0

Hi eXist users,

Here at the University of Richmond, we still use the old eXist version - eXist 2.1. Now we need to upgrade to the latest one - eXist 6.2.0; what would be your recommendation to upgrade from 2.1 to 6.2.0?

Thanks

--
Alem T. Areki
Senior Web Developer – Web Services
University of Richmond





_______________________________________________

Exist-open mailing list

[email protected]<mailto:[email protected]>

https://lists.sourceforge.net/lists/listinfo/exist-open

--

Pieter Lamers

John Benjamins Publishing Company

Postal Address: P.O. Box 36224, 1020 ME AMSTERDAM, The Netherlands

Visiting Address: Klaprozenweg 75G, 1033 NN AMSTERDAM, The Netherlands

Warehouse: Kelvinstraat 11-13, 1446 TK PURMEREND, The Netherlands

tel: +31 20 630 4747

web: www.benjamins.com<http://www.benjamins.com>
_______________________________________________
Exist-open mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/exist-open

_______________________________________________
Exist-open mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/exist-open