[
https://issues.apache.org/jira/browse/SOLR-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792341#action_12792341
]
Erik Hatcher commented on SOLR-1668:
------------------------------------
Another thought here is to make these configurations later-bound, if that makes
sense. Suppose I want something like:
stopWordFile="${company.code}_stopwords.txt"
Maybe a bit of a stretch of an example, with the fabricated idea that you want
to have a single Solr configuration (schema, etc) and be able to launch
multiple solr instances (can you do this with per-core params too? maybe so)
that use the same config, but use a different stop word list.
We'd have setStopWordList(SolrFile f), and we'd only that setter after the
system properties were in the mix.
Maybe this is neither here nor there as far as this issue is concerned, as the
property substitution is at a previous step no matter what, just wanted to make
sure this use case is kept in mind too.
> Declarative configuration meta-data for Solr plugins
> ----------------------------------------------------
>
> Key: SOLR-1668
> URL: https://issues.apache.org/jira/browse/SOLR-1668
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Affects Versions: 1.4
> Reporter: Uri Boness
> Priority: Minor
> Fix For: 1.5
>
> Attachments: commons-beanutils-1.8.2.jar, SOLR-1668.patch
>
>
> The idea here is for plugins in Solr to carry more meta data over their
> configuration. This can be very useful for building tools around Solr where
> this meta data can be used to assist users in configuring solr. One common
> mechanism to provide this meta data is by using standard Java Beans for the
> different configuration constructs where the properties define the
> configurable attributes and annotations are used to provide extra information
> about them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
