I really appreciate your suggestions and answers 
robip...@gmail.com<mailto:robip...@gmail.com> and ufuk yılmaz.

For a fresh 9.8 Solr, is it ok to install it on the same server with a 
different port? And, is there any method to transfer the indexed data between 
instances? I’m just learning about how Solr works so maybe these questions 
don’t much sense at all.

Thanks!

Regards,

Francisco Javier Alvarado Alonso
JAVA Apps Dev Sr  – BT West
Gulfstream Aerospace
Mexicali, Baja California 21376
Work Cellphone: +52 686 221 8824

From: ufuk yılmaz <uyil...@vivaldi.net.INVALID>
Sent: Friday, July 18, 2025 7:41 PM
To: users@solr.apache.org
Cc: francisco.alvaradoalo...@gulfstream.com.invalid; solr-u...@lucene.apache.org
Subject: Re: Solr upgrade from 8.x to 9.x

Here is a street approach. Reading and especially understanding every change in 
all of the release notes can be painful if you are not familiar with every area 
of Solr. Spin up a fresh 9. 8 Solr somewhere with the same configuration of 
your existing
ZjQcmQRYFpfptBannerStart
CAUTION: This email originated from outside the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.
    Report Suspicious  
<https://us-phishalarm-ewt.proofpoint.com/EWT/v1/LnUEiqHeOzE!tbTJPkNUouCycgDLgoiGJeuq14mdMrCQzEeSMUF3sWIo7nOJ6wwYIWl_LbxVovzzCm4AUcja2kEOYRkIvlmIZp4D8IUN2kaJYiQ6aUz8PCGxX5bE2n8$>
   ‌
ZjQcmQRYFpfptBannerEnd

Here is a street approach. Reading and especially understanding every change in 
all of the release notes can be painful if you are not familiar with every area 
of Solr. Spin up a fresh 9.8 Solr somewhere with the same configuration of your 
existing one, same solrconfig, same schema etc. Index a portion of your data, 
connect your system to this Solr and test your app. If there is anything 
obviously wrong, it should show up by now, and you can focus on that breaking 
change specifically and think about how to resolve that. The rest will probably 
be a corner case or a seldom used feature you forgot to verify..



Solr has many features and people use very different subsets of those so it is 
hard to say what might break or not after an upgrade.



—



> On Jul 19, 2025, at 11:01, Robi Petersen 
> <robip...@gmail.com<mailto:robip...@gmail.com>> wrote:

> Hi Francisco,

>

> Look here:

> https://urldefense.com/v3/__https://solr.apache.org/guide/solr/latest/upgrade-notes/solr-upgrade-notes.html__;!!LnUEiqHeOzE!K5oqxxVRzPENjUNYOq9L4kkxhdLOBHx5XP8r0ZFqNk-8O7ovUKsJmf-bbSn0QPIF1oYvYKKZ6AcbDE5YZf1zcEp3gWvRFU8BZlfb7yY$<https://urldefense.com/v3/__https:/solr.apache.org/guide/solr/latest/upgrade-notes/solr-upgrade-notes.html__;!!LnUEiqHeOzE!K5oqxxVRzPENjUNYOq9L4kkxhdLOBHx5XP8r0ZFqNk-8O7ovUKsJmf-bbSn0QPIF1oYvYKKZ6AcbDE5YZf1zcEp3gWvRFU8BZlfb7yY$>

>

> But note the changes before starting:

> https://urldefense.com/v3/__https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html__;!!LnUEiqHeOzE!K5oqxxVRzPENjUNYOq9L4kkxhdLOBHx5XP8r0ZFqNk-8O7ovUKsJmf-bbSn0QPIF1oYvYKKZ6AcbDE5YZf1zcEp3gWvRFU8BrtDsH9I$<https://urldefense.com/v3/__https:/solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-solr-9.html__;!!LnUEiqHeOzE!K5oqxxVRzPENjUNYOq9L4kkxhdLOBHx5XP8r0ZFqNk-8O7ovUKsJmf-bbSn0QPIF1oYvYKKZ6AcbDE5YZf1zcEp3gWvRFU8BrtDsH9I$>

>

> Best Regards

> Robi

>

> On Fri, Jul 18, 2025 at 5:52 PM AlvaradoAlonso, Francisco

> <francisco.alvaradoalo...@gulfstream.com.invalid<mailto:francisco.alvaradoalo...@gulfstream.com.invalid>>
>  wrote:

>

>> Hi Everyone,

>>

>> Does anyone have the detailed steps to upgrade Solr 8.x to 9.x in a

>> On-Prem clustered environment? If possible, with the most obvious

>> steps/tasks please.

>>

>>

>> Thank you in Advance,

>>

>>

>> Regards,

>>

>> Francisco Javier Alvarado Alonso

>> JAVA Apps Dev Sr  - BT West

>> Gulfstream Aerospace

>> Mexicali, Baja California 21376

>> Work Cellphone: +52 686 221 8824

>>

>> This e-mail message, including all attachments, is for the sole use of the

>> intended recipient(s) and may contain Personal Information under General

>> Dynamics policy CP 07-105 and/or legally privileged and confidential

>> information. Any Personal Information can be accessed only by authorized

>> personnel of General Dynamics and its approved service providers and may be

>> used only as permitted by General Dynamics and its policies. Contractual

>> restrictions apply to third parties. If you are not an intended recipient,

>> you are hereby notified that you have either received this message in error

>> or through interception, and that any review, use, distribution, copying or

>> disclosure of this message or its attachments is strictly prohibited and is

>> subject to criminal and civil penalties. All personal messages express

>> solely the sender's views and not those of Gulfstream Aerospace

>> Corporation. If you received this message in error, please contact the

>> sender by reply e-mail and destroy all copies of the original message.



This e-mail message, including all attachments, is for the sole use of the 
intended recipient(s) and may contain Personal Information under General 
Dynamics policy CP 07-105 and/or legally privileged and confidential 
information. Any Personal Information can be accessed only by authorized 
personnel of General Dynamics and its approved service providers and may be 
used only as permitted by General Dynamics and its policies. Contractual 
restrictions apply to third parties. If you are not an intended recipient, you 
are hereby notified that you have either received this message in error or 
through interception, and that any review, use, distribution, copying or 
disclosure of this message or its attachments is strictly prohibited and is 
subject to criminal and civil penalties. All personal messages express solely 
the sender's views and not those of Gulfstream Aerospace Corporation. If you 
received this message in error, please contact the sender by reply e-mail and 
destroy all copies of the original message.

Reply via email to