Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <241350927.1261110498073.JavaMail.jira@brutus>
Date: Fri, 18 Dec 2009 04:28:18 +0000 (UTC)
From: "Erik Hatcher (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1668) Declarative configuration meta-data
 for Solr plugins
In-Reply-To: <1756726611.1261098618352.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Erik Hatcher commented on SOLR-1668:
------------------------------------

Yeah, for sure annotations make sense to leverage here for part of it.  

As for user vs. code friendly - I'm of the opinion that they can be one and the same basically.  setStopWordFile(SolrFile f) has a lot of metadata in it.  Why not simply File?  I just figured we might want to abstract that one step from file system directness.

@Required makes sense for mandatory ones, indeed.  This is (with my dated knowledge of Ant internals) where Ant does the runtime kinda validation in the execute() method for a Task.  Maybe they've gone a step further with annotations now?  

And having a mechanism to override the parameter name or key, sure - but as much should be induced from the method signature as possible.  Making it a rich descriptive interface.

> 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.