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> 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 Dixit
ofbiz.apache.org
