lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] [Updated] (SOLR-4622) deprecate usage of DEFAULT_HOST_CONTEXT and DEFAULT_HOST_PORT
Date Thu, 18 Apr 2013 17:58:14 GMT


Hoss Man updated SOLR-4622:

    Attachment: SOLR-4622__phase3_trunk_only.patch

attached a trunk only patch for implementing phrase#3 of hte original proposal.  (been holding
off while a lot of CoreContainer/solr.xml stuff was up in the air)

All tests pass, i'll commit once 4.3 is closer to fully baked so as to not make things hard
for any last minute bug fix backports.
> -------------------------------------------------------------
>                 Key: SOLR-4622
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>             Fix For: 4.3, 5.0
>         Attachments: SOLR-4622.patch, SOLR-4622__phase3_trunk_only.patch
> Frequently, people who try to use solr cloud in a differnet servlet container (or in
a jetty other then the preconfigured one supplied) they can be easily confused as to why/how/where
solr is trying to hostContext=solr and hostPort=8983.
> these can be explicitly overridden in solr.xml, and the defaults are setup to read from
system properties, but we should eliminate the hardcoded defaults from the java code (where
most users can't even grep for them) and instead specify defaults for the sys properties in
the example configs.

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

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

View raw message