[
https://issues.apache.org/jira/browse/SOLR-6478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121305#comment-14121305
]
Grant Ingersoll edited comment on SOLR-6478 at 9/4/14 12:44 PM:
----------------------------------------------------------------
I suspect some of the URLs, etc. get a little wonky when you allow things like
spaces, etc. in the names. Not sure if we should allow them or not.
was (Author: gsingers):
I suspect ome of the URLs, etc. get a little wonky when you allow things like
spaces, etc. in the names. Not sure if we should allow them or not.
> need docs / tests of the "rules" as far as collection names go
> --------------------------------------------------------------
>
> Key: SOLR-6478
> URL: https://issues.apache.org/jira/browse/SOLR-6478
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
>
> historically, the rules for "core" names have been vague but implicitly
> defined based on the rule that it had to be a valid directory path name - but
> i don't know that we've ever documented anywhere what the rules are for a
> "collection" name when dealing with the Collections API.
> I haven't had a chance to try this, but i suspect that using the Collections
> API you can create any collection name you want, and the zk/clusterstate.json
> data will all be fine, and you'll then be able to request anything you want
> from that collection as long as you properly URL escape it in your request
> URLs ... but we should have a test that tries to do this, and document any
> actual limitations that pop up and/or fix those limitations so we really can
> have arbitrary collection names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
