lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shalin Shekhar Mangar (JIRA)" <>
Subject [jira] Resolved: (SOLR-921) SolrResourceLoader must cache short name vs fully qualified name
Date Wed, 18 Feb 2009 06:55:02 GMT


Shalin Shekhar Mangar resolved SOLR-921.

    Resolution: Fixed

Committed revision 745394.

Thanks Noble and Hoss!

> SolrResourceLoader must cache short name vs fully qualified name
> ----------------------------------------------------------------
>                 Key: SOLR-921
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Noble Paul
>            Assignee: Shalin Shekhar Mangar
>             Fix For: 1.4
>         Attachments: SOLR-921.patch, SOLR-921.patch, SOLR-921.patch, SOLR-921.patch
> every class that is loaded through SolrResourceLoader does a Class.forName() and when
if it is not found a ClassNotFoundExcepton is thrown
> Then , it looks up with the various packages and finds the right class if the name starts
with solr. Considering the fact that we usually use this solr.<classname> format we
pay too much of a price for this. After every lookup the result can be cached in a static
Map<String, String> with short name as keys and fully qualified name as values and can
be shared across all the cores and this Map can be stored at the CoreContainer level.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message