I would like to have a higher level discussion about the integration before mucking about in the SOLR code again. This way work invested is work that will not have to be changed too much later on. Do folks have ideas about how they would want to do this?
On Fri, Sep 5, 2008 at 7:03 AM, Noble Paul നോബിള് नोब्ळ् <[EMAIL PROTECTED]> wrote: > MultiCore.java is renamed to CoreContainer > > and SolrCore is changed a lot > > On Fri, Sep 5, 2008 at 4:27 PM, Jason Rutherglen (JIRA) <[EMAIL PROTECTED]> > wrote: >> >> [ >> https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628613#action_12628613 >> ] >> >> Jason Rutherglen commented on SOLR-567: >> --------------------------------------- >> >> Without looking at the code, what has changed? >> >>> SolrCore Pluggable >>> ------------------ >>> >>> Key: SOLR-567 >>> URL: https://issues.apache.org/jira/browse/SOLR-567 >>> Project: Solr >>> Issue Type: Improvement >>> Affects Versions: 1.3 >>> Reporter: Jason Rutherglen >>> Attachments: solr-567.patch, solr-567.patch >>> >>> >>> SolrCore needs to be an abstract class with the existing functionality in a >>> subclass. SolrIndexSearcher the same. It seems that most of the Searcher >>> methods in SolrIndexSearcher are not used. The new abstract class need >>> only have the methods used by the other Solr classes. This will allow >>> other indexing and search implementations to reuse the other parts of Solr. >>> Any other classes that have functionality specific to the Solr >>> implementation of indexing and replication such as SolrConfig can be made >>> abstract. >> >> -- >> This message is automatically generated by JIRA. >> - >> You can reply to this email to add a comment to the issue online. >> >> > > > > -- > --Noble Paul >
