[
https://issues.apache.org/jira/browse/SOLR-6365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14095367#comment-14095367
]
Noble Paul edited comment on SOLR-6365 at 8/13/14 11:19 AM:
------------------------------------------------------------
bq.Where do I say that path=/search should be used for searching
No, users don't say what is the there in the path {{/search}} . we should
decide it for the users. But if the users insist on doing that they can do
that.
BTW you should look at SOLR-6191 and apply the patch and play with it . if know
any path and append {{/meta}} to that path and you will get the documentation
on that path.
for instance {{/meta}} will tell you all the registered paths at the root. And
{{/select}} will be listed there . If you hit {{/select/meta}} it will describe
the capabilities+ params for {{/select}}
And planning to add more things such as {{/select/meta/stats}} should give you
stats for {{/select}}
was (Author: noble.paul):
bq.Where do I say that path=/search should be used for searching
No, you don't say , what is the there in the path {{/search}} we should decide
it for the users. But if the users insist on doing that they can do that.
BTW you should look at SOLR-6191 and apply the patch and play with it . if know
any path and append {{/meta}} to that path and you will get the documentation
on that path.
for instance {{/meta}} will tell you all the registered paths at the root. And
{{/select}} will be listed there . If you hit {{/select/meta}} it will describe
the capabilities+ params for {{/select}}
And planning to add more things such as {{/select/meta/stats}} should give you
stats for {{/select}}
> specify appends, defaults, invariants outside of the component
> ---------------------------------------------------------------
>
> Key: SOLR-6365
> URL: https://issues.apache.org/jira/browse/SOLR-6365
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
> Assignee: Noble Paul
>
> The components are configured in solrconfig.xml mostly for specifying these
> extra parameters. If we separate these out, we can avoid specifying the
> components altogether and make solrconfig much simpler. Eventually we want
> users to see all funtions as paths instead of components and control these
> params from outside , through an API and persisted in ZK
> example
> {code:xml}
> <!-- these are top level tags not specified inside any components -->
> <params path="/dataimport" defaults="config=data-config.xml"/>
> <params path="/update/*" defaults="wt=json"/>
> <params path="/some-other-path/*" defaults="a=b&c=d&e=f" invariants="x=y"
> appends="i=j"/>
> <!-- use json for all paths and _txt as the default search field-->
> <params path="/**" defaults="wt=json&df=_txt" />
> {code}
> The idea is to use the parameters in the same format as we pass in the http
> request and eliminate specifying our default components in solrconfig.xml
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
