[
https://issues.apache.org/jira/browse/SOLR-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16480740#comment-16480740
]
Shawn Heisey commented on SOLR-6733:
------------------------------------
Solr's install directory layout will be altered significantly with these
changes. The new service installer script is going to need an upgrade option,
which can optionally take an old service name. The script would then find the
old service, read its config, and duplicate as much of that config as it can
for the new service.
I've been having a discussion with docker-solr on how to benefit both projects.
https://github.com/docker-solr/docker-solr/issues/173
> Umbrella issue - Solr as a standalone application
> -------------------------------------------------
>
> Key: SOLR-6733
> URL: https://issues.apache.org/jira/browse/SOLR-6733
> Project: Solr
> Issue Type: New Feature
> Reporter: Shawn Heisey
> Priority: Major
>
> Umbrella issue.
> Solr should be a standalone application, where the main method is provided by
> Solr source code.
> Here are the major tasks I envision, if we choose to embed Jetty:
> * Create org.apache.solr.start.Main (and possibly other classes in the same
> package), to be placed in solr-start.jar. The Main class will contain the
> main method that starts the embedded Jetty and Solr. I do not know how to
> adjust the build system to do this successfully.
> * Handle central configurations in code -- TCP port, SSL, and things like
> web.xml.
> * For each of these steps, clean up any test fallout.
> * Handle cloud-related configurations in code -- port, hostname, protocol,
> etc. Use the same information as the central configurations.
> * Consider whether things like authentication need changes.
> * Handle any remaining container configurations.
> I am currently imagining this work happening in a new branch and ultimately
> being applied only to master, not the stable branch.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
