You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2018/01/04 06:46:00 UTC

[jira] [Updated] (SOLR-11817) Move Collections API classes to it's own package

     [ https://issues.apache.org/jira/browse/SOLR-11817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Varun Thacker updated SOLR-11817:
---------------------------------
    Attachment: SOLR-11817.patch

Patch which moves collection api's to their own package including tests

There is lots of room for cleaning the code up and also making things more modular . But we can tackle that in separate Jiras. The patch is pretty big already because of all the shuffling

> Move Collections API classes to it's own package
> ------------------------------------------------
>
>                 Key: SOLR-11817
>                 URL: https://issues.apache.org/jira/browse/SOLR-11817
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Varun Thacker
>            Assignee: Varun Thacker
>            Priority: Minor
>         Attachments: SOLR-11817.patch
>
>
> Today all collections api classes and tests are in the {{org.apache.solr.cloud}} package.
> We should create a {{org.apache.solr.cloud.api.collections}} package and move the respected classes under that.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org