[ 
https://issues.apache.org/jira/browse/SOLR-12224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17925721#comment-17925721
 ] 

Jason Gerlowski edited comment on SOLR-12224 at 2/10/25 8:16 PM:
-----------------------------------------------------------------

I closed this out errantly as a duplicate of SOLR-16390, but that ticket turns 
out to be unrelated.  My mistake!

I *do* think that adding get and/or list collectionprop APIs would be great for 
v2 in particular, we just need a volunteer to help with that effort.  I'm more 
than happy to guide and help if someone's willing to drive development. 


was (Author: gerlowskija):
I closed this out errantly as a duplicate of SOLR-16390, but that ticket turns 
out to be unrelated.  My mistake!

> 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
>          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
(v8.20.10#820010)

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

Reply via email to