[
https://issues.apache.org/jira/browse/SOLR-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206869#comment-13206869
]
Erick Erickson commented on SOLR-3121:
--------------------------------------
bq: I think we can even remove the old schema browser (linking to the new one)
until we can get rid of the old one entirely
Doesn't this happen already? If I enter http://localhost:8983/ I go straight to
the new UI, although it *does* have a link to the old UI and the old URL goes
straight to the old Admin UI.
But yeah, it seems that cutting over to the new UI and letting the old one fade
away (or just remove it) is what should be done. The problem is, though, that
the new code is kind of intimidating if you're not fluent in js/jquery, but I
suppose it's just a matter of getting used to it.
And SOLR-3116 is a known issue. I expect that SolrCloud will get a lot of
traffic when 4.0 is released, so this seems critical if we're to really cut
over.
Anyway, I'll commit this patch today sometime unless someone beats me to it.
> Make new admin UI work better with big indexes
> ----------------------------------------------
>
> Key: SOLR-3121
> URL: https://issues.apache.org/jira/browse/SOLR-3121
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 4.0
> Reporter: Ryan McKinley
> Fix For: 4.0
>
> Attachments: SOLR-3121-luke-admin-ui.patch,
> SOLR-3121-luke-admin-ui.patch, SOLR-3121.patch, SOLR-3121.patch
>
>
> As reported in SOLR-2667, the admin UI gets pretty bad with big indexes.
> Mostly this seems the fault of excessive calls to luke and not limiting the
> number of terms
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
