lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Biestro (JIRA)" <j...@apache.org>
Subject [jira] Updated: (SOLR-350) Manage Multiple SolrCores
Date Mon, 21 Jul 2008 17:15:33 GMT

     [ https://issues.apache.org/jira/browse/SOLR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Henri Biestro updated SOLR-350:
-------------------------------

    Attachment: solr-350-properties.patch

This patch (solr-350-properties.patch) implements 'properties' as specified by [HossMan|https://issues.apache.org/jira/browse/SOLR-350?focusedCommentId=12562834#action_12562834].

This means configuration & schema files can use expression based on properties defined
in multicore.xml.


Multicore.xml can define properties at the multicore & each core level.
Properties defined in the multicore scope can override system properties.
Properties defined in a core scope can override multicore & system properties.
Property definitions can use expressions to define their name & value; these expressions
are evaluated in their outer scope context .
Multicore serialization keeps properties as written (ie as expressions if they were defined
so).

The core descriptor properties are automatically  defined in each core context, namely:
solr.core.instanceDir
solr.core.instancePath
solr.core.name
solr.core.configName
solr.core.schemaName

The code itself refactored some of DOMUtil (the ant based property substitution) into one
added class (PropertyMap & PropertyMap.Evaluator).
The PropertyMap are chained (one link chain between core to multicore map); those maps are
owned by each core's ResourceLoader.
Config is modified a little to accomodate delaying & specializing property expansions.


Reviews & comments more than welcome.
PS: Should we open a new issue or re-open this one to track progress ?


> Manage Multiple SolrCores
> -------------------------
>
>                 Key: SOLR-350
>                 URL: https://issues.apache.org/jira/browse/SOLR-350
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 1.3
>            Reporter: Ryan McKinley
>            Assignee: Ryan McKinley
>             Fix For: 1.3
>
>         Attachments: SOLR-350-jsp-fixes.patch, SOLR-350-jsp-fixes.patch, SOLR-350-MultiCore.patch,
SOLR-350-MultiCore.patch, SOLR-350-MultiCore.patch, SOLR-350-Naming.patch, SOLR-350-Naming.patch,
solr-350-properties.patch, SOLR-350-RemoveStatic.patch, solr-350.patch, solr-350.patch, solr-350.patch,
solr-350.patch, solr-350.patch, solr-350.patch, solr-350.patch, solr-350.patch, solr-350.patch,
solr-350.patch, solr-350.patch, solr-350.patch, solr-350.patch, solr-350.patch
>
>
> In SOLR-215, we enabled support for more then one SolrCore - but there is no way to use
them yet.
> We need to make some interface to manage, register, modify avaliable SolrCores

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message