i generally will only upgrade every other release. since i started with 1.4, went to 3->5->7.X, and never EVER a .0 or an even .X release,
On Fri, Feb 12, 2021 at 12:01 PM Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > Just avoid 8.8.0 for the moment, until 8.8.1 is released. 8.7.x should be > fine. > > On Fri, Feb 12, 2021 at 10:28 PM Alessandro Benedetti < > a.benede...@sease.io> > wrote: > > > Hi, > > following up on Charlie's detailed response I would recommend carefully > > assess the code you are using to interact with Apache Solr (on top of the > > Solr changes themselves). > > Assuming you are using some sort of client, it's extremely important to > > fully understand both the syntax and semantic of each call. > > I saw a lot of "compiling ok" search-api migrations that were ok > > syntactically but doing a disaster from the semantic perspective (missing > > important parameters ect). > > > > In case you have plugins to maintain this would be even more complicated > > than just make them compile. > > > > Regards > > -------------------------- > > Alessandro Benedetti > > Apache Lucene/Solr Committer > > Director, R&D Software Engineer, Search Consultant > > www.sease.io > > > > > > On Tue, 9 Feb 2021 at 11:01, Charlie Hull < > ch...@opensourceconnections.com > > > > > wrote: > > > > > Hi Lulu, > > > > > > I'm afraid you're going to have to recognise that Solr 5.2.1 is very > > > out-of-date and the changes between this version and the current 8.x > > > releases are significant. A direct jump is I think the only sensible > > > option. > > > > > > Although you could take the current configuration and attempt to > upgrade > > > it to work with 8.x, I recommend that you should take the chance to > look > > > at your whole infrastructure (from data ingestion through to query > > > construction) and consider what needs upgrading/redesigning for both > > > performance and future-proofing. You shouldn't just attempt a > > > lift-and-shift of the current setup - some things just won't work and > > > some may lock you into future issues. If you're running at large scale > > > (I've talked to some people at the BL before and I know you have some > > > huge indexes there!) then a redesign may be necessary for scalability > > > reasons (cost and feasibility). You should also consider your skills > > > base and how the team can stay up to date with Solr changes and modern > > > search practice. > > > > > > Hope this helps - this is a common situation which I've seen many times > > > before, you're certainly not the oldest version of Solr running I've > > > seen recently either! > > > > > > best > > > > > > Charlie > > > > > > On 09/02/2021 01:14, Paul, Lulu wrote: > > > > Hi SOLR team, > > > > > > > > Please may I ask for advice regarding upgrading the SOLR version (our > > > project currently running on solr-5.2.1) to the latest version? > > > > What are the steps, breaking changes and potential issues ? Could > this > > > be done as an incremental version upgrade or a direct jump to the > newest > > > version? > > > > > > > > Much appreciate the advice, Thank you! > > > > > > > > Best Wishes > > > > Lulu > > > > > > > > > > > > > > > > > > ****************************************************************************************************************** > > > > Experience the British Library online at www.bl.uk<http://www.bl.uk/ > > > > > > The British Library's latest Annual Report and Accounts : > > > www.bl.uk/aboutus/annrep/index.html< > > > http://www.bl.uk/aboutus/annrep/index.html> > > > > Help the British Library conserve the world's knowledge. Adopt a > Book. > > > www.bl.uk/adoptabook<http://www.bl.uk/adoptabook> > > > > The Library's St Pancras site is WiFi - enabled > > > > > > > > > > ***************************************************************************************************************** > > > > The information contained in this e-mail is confidential and may be > > > legally privileged. It is intended for the addressee(s) only. If you > are > > > not the intended recipient, please delete this e-mail and notify the > > > postmas...@bl.uk<mailto:postmas...@bl.uk> : The contents of this > e-mail > > > must not be disclosed or copied without the sender's consent. > > > > The statements and opinions expressed in this message are those of > the > > > author and do not necessarily reflect those of the British Library. The > > > British Library does not take any responsibility for the views of the > > > author. > > > > > > > > > > ***************************************************************************************************************** > > > > Think before you print > > > > > > > > > > -- > > > Charlie Hull - Managing Consultant at OpenSource Connections Limited > > > <www.o19s.com> > > > Founding member of The Search Network <https://thesearchnetwork.com/> > > > and co-author of Searching the Enterprise > > > <https://opensourceconnections.com/about-us/books-resources/> > > > tel/fax: +44 (0)8700 118334 > > > mobile: +44 (0)7767 825828 > > > > > >
