[ https://issues.apache.org/jira/browse/SOLR-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14709479#comment-14709479 ]
Erick Erickson commented on SOLR-4316: -------------------------------------- bq: Would that work? Then, if people are happy with that, I can complete this task and get on with working on the collections Let's do the minimum necessary to cut over to the new Angular JS version. I think it's important to get people using that version, flush out any lingering issues then move on with improvements rather than wait for new functionality. FWIW > Admin UI - SolrCloud - extend core options to collections > --------------------------------------------------------- > > Key: SOLR-4316 > URL: https://issues.apache.org/jira/browse/SOLR-4316 > Project: Solr > Issue Type: Improvement > Components: web gui > Affects Versions: 4.1 > Reporter: Shawn Heisey > Assignee: Upayavira > Fix For: 4.9, Trunk > > Attachments: SOLR-4316.patch, SOLR-4316.patch, collections menu > open.png, cores menu open.png, solrcloud-admin-ui-menu.png, two-selectors.png > > > There are a number of sections available when you are looking at a core in > the UI - Ping, Query, Schema, Config, Replication, Analysis, Schema Browser, > Plugins / Stats, and Dataimport are the ones that I can see. > A list of collections should be available, with as many of those options that > can apply to a collection, If options specific to collections/SolrCloud can > be implemented, those should be there too. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org