lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-3613) Namespace Solr's JAVA OPTIONS
Date Wed, 11 Jul 2012 15:46:35 GMT


Mark Miller commented on SOLR-3613:

I'd been considering this issue some myself after coming across an email from Jan way back
on the mailing list.

On the whole, just being consistent made sense to me, but I was weighing that vs changing
things on everyone already out there using the current stuff, a couple blog posts, talks,
etc. This stuff has been out there long enough that we want to weigh the pros and cons of
a hard break. I thought about back compat support even though this is trunk and it's not required.

Then I figured we should still do it if we wanted to be just a webapp. But I've been convinced
that Solr will be better if we treat it as an app itself instead of a webapp. I really don't
see the point in trying to support running other webapps with Solr - it should be the only
thing running in it's process. It's a search engine.

By moving towards the position of Solr being an app and not a war, I think we can make many
things nicer and more user friendly for little to no downside.
> Namespace Solr's JAVA OPTIONS
> -----------------------------
>                 Key: SOLR-3613
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.0-ALPHA
>            Reporter: Jan H√łydahl
>             Fix For: 4.0
> Solr being a web-app, should play nicely in a setting where users deploy it on a shared
> To this regard Solr's JAVA_OPTS should be properly name spaced, both to avoid name clashes
and for clarity when reading your appserver startup script. We currently do that with most:
{{solr.solr.home,, solr.abortOnConfigurationError, solr.directoryFactory, solr.clustering.enabled,
solr.velocity.enabled etc}}, but for some opts we fail to do so.
> Before release of 4.0 we should make sure to clean this up.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message