[
https://issues.apache.org/jira/browse/SOLR-4534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13596290#comment-13596290
]
Mark Miller commented on SOLR-4534:
-----------------------------------
Hey Steve - I of course prefer that type of format, but it's not really
consistent with the current admin API's. So initially, I think I might favor
being more consistent - I think it would be more awkward for the shard and
collection aliasing to be so different than with the new schema api not being
consistent - depending on how long this takes to get in.
However, I would like to change the current admin API's to all work closer to
what your suggesting now that you have gotten restlet in.
I was thinking to deal with back compat, I could just make new apis and keep
the old ones around, but deprecate and remove for 5 or something.
I know it's a big deal to change the API's, but it would just be admin side,
not search, and it would be a big step forward I think. The current admin API's
are fairly unusual.
> Shard Aliasing
> --------------
>
> Key: SOLR-4534
> URL: https://issues.apache.org/jira/browse/SOLR-4534
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Reporter: Mark Miller
>
> Collection Aliasing lets you do some interesting things, but all of it
> requires multiple collections. It's also interesting to be able to alias
> shards within a collection so that you don't always have to use multiple
> collections to take advantage of aliasing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
