[
https://issues.apache.org/jira/browse/SOLR-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873381#action_12873381
]
Hoss Man commented on SOLR-1931:
--------------------------------
bq. I can't find where the index is scanned
take a look at getIndexInfo and it's "countTerms" boolean
by the looks of how it's used, it seems like the assumption was that if the
numTerms param != 0, then you're clearly okay with it taking some time, so it
might as well compute the total number of terms in the index for you -- but the
default value of numTerms is "20", so in the "/admin/luke?show=schema" case, it
computes the total number of terms even though it isn't finding top terms for
any field.
if we just add an explicit "countTerms" boolean param that should make it
possible to speed things up a lot.
> Schema Browser does not scale with large indexes
> ------------------------------------------------
>
> Key: SOLR-1931
> URL: https://issues.apache.org/jira/browse/SOLR-1931
> Project: Solr
> Issue Type: Improvement
> Components: web gui
> Affects Versions: 1.4
> Reporter: Lance Norskog
> Priority: Minor
>
> The Schema Browser JSP by default causes the Luke handler to "scan the
> world". In large indexes this make the UI useless.
> On an index with 64m documents & 8gb of disk space, the Schema Browser took 6
> minutes to open and hogged all disk I/O, making Solr useless.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
