[
https://issues.apache.org/jira/browse/SOLR-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088891#comment-14088891
]
Shalin Shekhar Mangar commented on SOLR-6191:
---------------------------------------------
I think we should split this issue into two APIs:
# A node capabilities API which returns all the paths and the request handlers
supported by a node
# A method introspection API which returns all the parameters required for a
method.
They might actually be one API endpoint but this will simplify the development
because #1 just needs the information in solrconfig.xml and no annotations or
interfaces are necessary. #2 can be implemented after the implementation
details are fleshed out. Another reason for asking this separation is that I am
blocked by the need of #1 for SOLR-6235.
> 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
