Yup indeed there's a lot less JSON.

But are we able to configure this somewhere permanently?
Normally I don't query the ZooKeeper in my URL directly for my query.

Regards,
Edwin


On 5 June 2015 at 21:04, Shawn Heisey <apa...@elyograg.org> wrote:

> On 6/5/2015 1:46 AM, Zheng Lin Edwin Yeo wrote:
> > That's why we are trying to get the user to change something else instead
> > of the collection name. The collection alias sounds like a good option.
> >
> > Is there a way to list out all the alias names, or the only way is to
> > reference it at aliases.json file under the Cloud section in the Admin
> UI?
> >
> > As when I use the /admin/collections?action=LIST, it list the collection
> > names only, and I'm using this to populate the collections on the UI
> > dynamically. If the user is using the alias name, there's no need for
> them
> > to know the actual collection name. So I'm trying to find a way is there
> a
> > way to list out all the alias name.
>
> This is what the admin UI uses when it retrieves aliases.json to show it
> to you within the Cloud->Tree section:
>
> http://server:port/solr/zookeeper?detail=true&path=%2Faliases.json
>
> If you remove detail=true from that URL, there will be a lot less JSON
> to parse:
>
> http://server:port/solr/zookeeper?path=%2Faliases.json
>
> You'll need to figure out how to send that request with whatever Solr or
> HTTP client you are using, and then you will probably need to parse the
> JSON to get the information.
>
> If your client is SolrJ, it might offer an easier way to grab that
> information ... but I'm not familiar enough with the code to say for sure.
>
> Thanks,
> Shawn
>
>

Reply via email to