lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-6733) Umbrella issue - Solr as a standalone application
Date Tue, 15 May 2018 19:51:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-6733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476392#comment-16476392
] 

Shawn Heisey commented on SOLR-6733:
------------------------------------

I think that embedding Jetty is the path of least resistance, and least likely to cause heartburn.
 If there is any desire to switch to some other way of providing http services, it would be
best to decide that before doing any work on this.

Pluses to embedding Jetty:  A lot of the code is already written, and more importantly, debugged.
 The Jetty community has been really awesome.  They respond quickly to requests on their mailing
list and IRC channel, with helpful answers.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message