Hi Nicolas, Thanks for your kind words! I really appreciate your offer to push it to the wiki. But, I’d like to take the initiative to add it myself.
I'll make sure to update the wiki soon and will share the link once it's live. Please let me know if you have any suggestions or improvements to include! Kind regards, Ayan Farooqui Product Engineer *HotWax Commerce* *Real OmniChannel. Real Results.* email: ayan.faroo...@hotwax.co *www.hotwax.co <http://www.hotwax.co/>* On Fri, Mar 21, 2025 at 3:17 PM Nicolas Malin <nicolas.ma...@nereide.fr> wrote: > Hello Ayan, > > Thanks for this sharing, it's really cool. > > I thinks it's a good work to push on the wiki. If you didn't plan it I can > do it ? > > Like that we start the plugin and jakarta migration :) > > Nicolas > > Le 20/03/2025 à 06:11, Ayan Farooqui a écrit : > > Hello All, > > I took the liberty of doing a POC to ensure a smooth transition from > embedded Solr to a standalone instance while maintaining data and > configuration integrity, here’s the process to follow: > > Before starting, stop Solr to prevent data corruption and file lock issues. > > 1. > > Copy Configuration > - > > Navigate to ${ofbiz.home}/plugins/solr/home/{YourCoreName} and copy > the core configuration. > - > > Paste it into your standalone Solr instance at > solr8.11.3/server/solr/{YourCoreName}. > 2. > > Copy Data > - > > Locate the <dataDir> tag in solrconfig.xml to find the existing data > directory. > - > > Defaults to -${ofbiz.home}/runtime/indexes/solr/products/ > - > > Copy its contents and paste them into > solr8.11.3/server/solr/{YourCoreName}/data/. > 3. > > Update Data Directory > Modify - solr8.11.3/server/solr/{YourCoreName}/conf/solrconfig.xml file to > set the data directory to Solr’s default or a custom path: Solr Default > - <dataDir>${solr.data.dir:}</dataDir> Points to - > solr8.11.3/server/solr/{YourCoreName}/data/. (where we copied the data) If > you have copied the core data to a custom path then specify that data > directory > > > Once these steps are complete, start the standalone Solr instance, and your > data should be intact. > > Kind regards, > Ayan Farooqui > Product Engineer > *HotWax Commerce* > *Real OmniChannel. Real Results.* > email: ayan.faroo...@hotwax.co > *www.hotwax.co <http://www.hotwax.co/> <http://www.hotwax.co/>* > > > On Sat, Mar 15, 2025 at 5:28 PM Anshul Goyal <anshe...@gmail.com> > <anshe...@gmail.com> wrote: > > > Hi Jacques, > > One of the projects I am working on uses solr in the embedded mode, and > I'll soon be migrating it to an external Solr instance. > I'll document all the important code changes needed, configurations > involved and challenges faced during the process. > > I lack knowledge of migration tools, if they're a better solution, I would > like to proceed that way as well. > > Anshul > > On Sat, 15 Mar 2025 at 13:17, Jacques Le Roux <jacques.le.r...@les7arts.com> > wrote: > > > Hi Anshul, > > I see no problem creating a Confluence page to start. Of course > implementing a migration tool would be better. > > Have someone ever done a Solr migration from the plugin to an external > Solr instance? > > Jacques > > Le 12/03/2025 à 13:39, Anshul Goyal a écrit : > > Hi Jacques, > > A confluence page can serve greatly to users needing migration. The > > amount > > of detail it would carry is a concern here. > > A few things those are completely different in the two are: > > 1. Core creation process flow > 2. Solr deployment process flow > 3. Directory locations in both cases > > We can start building a confluence page, and then add on to it in > progressive manner. > > Anshul > > On Wed, 12 Mar 2025, 17:22 Jacques Le Roux,< > > jacques.le.r...@les7arts.com > > wrote: > > > Hi, > > So what do we do? > > A Jira should be enough if we plan to implement a migration tool. That > still needs to be decided and then planned. > If we don't implement a migration tool a Confluence page would fit. > > But > > would that be enough? > > Should we vote about that? > > Jacques > > Le 11/03/2025 à 07:50, Chandan Khandelwal a écrit : > > Hello all, > > I agree with deprecating embedded Solr and providing a migration > > process > > for external Solr. This will allow us to move forward with the > > Jakarta > > migration. > > > Kind Regards, > Chandan Khandelwal > > > > On Mon, Mar 10, 2025 at 9:11 PM Anshul Goyal<anshe...@gmail.com> > <anshe...@gmail.com> > > wrote: > > Hi all, > > I too support providing a smooth transition for users of embedded > > version > > to the standalone version, keeping in mind that Jakarta migration > > is > > important and the lucene may update solr further. > > This seems like a good way to deal with it. > > Best regards > Anshul Goyal > > On Mon, 10 Mar 2025, 20:52 Jacopo Cappellato, < > > jacopo.cappell...@gmail.com > > wrote: > > > I also support the idea of deprecating the embedded mode of > > integrating > > SOLR. > To address Michael's concerns of existing users, we could provide > tools, mechanisms, or guidelines to help streamline the transition > from embedded to external SOLR. > > Jacopo > > On Mon, Mar 10, 2025 at 3:47 PM Michael Brohl < > > michael.br...@ecomify.de> > > wrote: > > Hi Deepak, > > I know that embedded Solr is used so that does not seem to be a > > valid > > solution. > > Best regards, > > Michael Brohl > > ecomify GmbH -www.ecomify.de > > Am 10.03.25 um 07:51 schrieb Deepak Dixit: > > We can update the Solr plugin to connect with an external Solr > > instance > > instead of running it embedded. I believe no one uses Solr in > > embedded > > mode > > in production, > so it's best to treat Solr as an external system. > With the Solr plugin update, we can configure it to communicate > > with > > an > > external Solr instance. > To make it developer-friendly, we can also provide a Gradle task > > to > > download and run Solr in the development environment. > > -- > Deepak Dixitofbiz.apache.org > > >
