We can get things like this in. If you want, feel free to have a go. As much as I want to work on funky new stuff, I really need to focus on finishing stuff first.
Upayavira On Wed, Jun 17, 2015, at 02:53 PM, Anshum Gupta wrote: > Also, while you are at it, it'd be good to get SOLR-4777 in so the Admin > UI > is correct when users look at the SolrCloud graph post an operation that > can leave the slice INACTIVE e.g. Shard split. > > On Wed, Jun 17, 2015 at 2:50 PM, Anshum Gupta <ans...@anshumgupta.net> > wrote: > > > This looks good overall and thanks for migrating it to something that more > > developers can contribute to. > > > > I started solr (trunk) in cloud mode using the bin scripts and opened the > > new admin UI. The section for 'cores' says 'No cores available. Go and > > create one'. > > Starting Solr 5.0, we officially stated in the change log and at other > > places that the only supported way to create a collection is through the > > Collections API. We should move along those lines and not stray with the > > new interface. I am not sure if the intention with this move is to first > > migrate everything as is and then redo the design but I'd strongly suggest > > that we do things the right way. > > > > On Sun, Jun 14, 2015 at 5:53 PM, Erick Erickson <erickerick...@gmail.com> > > wrote: > > > >> And anyone who, you know, really likes working with UI code please > >> help making it better! > >> > >> As of Solr 5.2, there is a new version of the Admin UI available, and > >> several improvements are already in 5.2.1 (release imminent). The old > >> admin UI is still the default, the new one is available at > >> > >> <solr_ip:port>/admin/index.html > >> > >> Currently, you will see very little difference at first glance; the > >> goal for this release was to have as much of the current functionality > >> as possible ported to establish the framework. Upayavira has done > >> almost all of the work getting this in place, thanks for taking that > >> initiative Upayavira! > >> > >> Anyway, the plan is several fold: > >> > Get as much testing on this as possible over the 5.2 time frame. > >> > Make the new Angular JS-based code the default in 5.3 > >> > Make improvements/bug fixes to the admin UI on the new code line, > >> particularly SolrCloud functionality. > >> > Deprecate the current code and remove it eventually. > >> > >> The new code should be quite a bit easier to work on for programmer > >> types, and there are Big Plans Afoot for making the admin UI more > >> SolrCloud-friendly. Now that the framework is in place, it should be > >> easier for anyone who wants to volunteer to contribute, please do! > >> > >> So please give it a whirl. I'm sure there will be things that crop up, > >> and any help addressing them will be appreciated. There's already an > >> umbrella JIRA for this work, see: > >> https://issues.apache.org/jira/browse/SOLR-7666. Please link any new > >> issues to this JIRA so we can keep track of it all as well as > >> coordinate efforts. If all goes well, this JIRA can be used to see > >> what's already been reported too. > >> > >> Note that things may be moving pretty quickly, so trunk and 5x will > >> always be the most current. That said looking at 5.2.1 will be much > >> appreciated. > >> > >> Erick > >> > > > > > > > > -- > > Anshum Gupta > > > > > > -- > Anshum Gupta
