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

Noble Paul commented on SOLR-6191:
----------------------------------

bq.I guess since {{Method.path}} defaults to empty it could be ignored by 
components
That is optional . It won't be enforced. Only for requesthandlers with fixed 
paths (We plan to fix it for some like, /admin/ping, /replication) we plan to 
provide this

bq.but maybe we should have another container annotation like {{Params}}
Yeah, I plan to add something like a {{ParamSet}} or Whatever. This must be 
taking care of the multiple pseudo methods handled by a single API example: 
CollectionHandler , COreAdminHandler 

bq.Handlers can be respond to multiple endpoints, which is configured in 
{{solrconfig.xml}}

Yes, You can lookup by path in solrconfig.xml . When the call is received, the 
component is looked up and the annotations are fetched at that point

bq.I think whatever solution we land on, it should be possible to fully 
describe parameters in a single place

Yes, absolutely

bq.E.g. when initializing and testing handlers/components, will annotations 
provide a clean interface to pull named parameters out

That is not taken care of.  I agree that it should








> 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
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to