Shawn Heisey commented on SOLR-12224:

If collection properties are part of CLUSTERSTATUS, the response could 
potentially be quite large.  If there are five hundred collections, each with a 
handful of properties, that's a lot of information.  Somebody who's after a 
quick cluster-wide status response probably isn't interested in all of that.  
Gathering it will also increase the response time.

I think it is best to allow the existing COLLECTIONPROP action to return the 
properties when the request is missing parameters, or create a new action 
specifically for listing them.

> there is no API to read collection properties
> ---------------------------------------------
>                 Key: SOLR-12224
>                 URL: https://issues.apache.org/jira/browse/SOLR-12224
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>    Affects Versions: 7.3
>            Reporter: Hendrik Haddorp
>            Priority: Major
> Solr 7.3 added the COLLECTIONPROP API call 
> (https://lucene.apache.org/solr/guide/7_3/collections-api.html#collectionprop)
>  that allows to set arbitrary properties on a collection. There is however no 
> API call that returns the data. The only option is to manually read out the 
> collectionprops.json file in ZK below the collection.
> Options could be that the COLLECTIONPROP command has an option to retrieve 
> properties, have a special command to list the properties and/or to have the 
> properties listed in the clusterstatus output for a collection.
> Would be great if SolrJ would also be supported.

This message was sent by Atlassian JIRA

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

Reply via email to