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

Vitaliy Zhovtyuk commented on SOLR-6191:
----------------------------------------

Annotation approach is beautiful, but it does not describe used in code 
parameter names since it just string constants. Original goal was to replace 
all parameter string names with strong typed enum containing parameter string 
description, see org.apache.solr.common.params.SolrParams. Probably make sense 
to use both ways and use Parameter enum implementing 
org.apache.solr.common.params.ParameterDescription as @Param value and don't 
require component to extend interface.

This will bring strong typing code usages and provide generic API for 
describing parameters.

> Self Describing SearchComponents, RequestHandlers, params. etc.
> ---------------------------------------------------------------
>
>                 Key: SOLR-6191
>                 URL: https://issues.apache.org/jira/browse/SOLR-6191
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Vitaliy Zhovtyuk
>            Assignee: Noble Paul
>              Labels: features
>         Attachments: SOLR-6191.patch, SOLR-6191.patch, SOLR-6191.patch, 
> SOLR-6191.patch
>
>
> We should have self describing parameters for search components, etc.
> I think we should support UNIX style short and long names and that you should 
> also be able to get a short description of what a parameter does if you ask 
> for INFO on it.
> For instance, &fl could also be &fieldList, etc.
> Also, we should put this into the base classes so that new components can add 
> to it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to