lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-6478) need docs / tests of the "rules" as far as collection names go
Date Thu, 04 Sep 2014 01:51:51 GMT
Hoss Man created SOLR-6478:
------------------------------

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


Mime
View raw message