[ 
https://issues.apache.org/jira/browse/STANBOL-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13774477#comment-13774477
 ] 

Rupert Westenthaler commented on STANBOL-1162:
----------------------------------------------

The main differences are:

* CoreConteiner#load() need to be called as it is no longer implicitly called 
by the used constructor. Not doing so will cause NPE in the QueryAnalyzer

* All AnalyzerFactories do no longer have a default constructor, but take a 
Map<String,String>. Previously this was parsed with the init() method
* This also means that one can no longer create an instance without an 
configuration. So it is no longer possible to directly register such factories 
as OSGI services (as required by the OSGI enabled SolrResourceLoader). To 
workaround that factory classes are now wrapped by the new 
"RegisteredSolrAnalyzerFactory". The RegisteredSolrAnalyzerFactory is registers 
as OSGI service.
* The same API change also required to adapt other components that where 
instantiating AnalyzerFactoreis (CharFilter, Tokenizer and/or TokenFilter)
* Solr 4.4. has some new dependencies that where added to the parent and also 
the bundlelist. 
                
> Update commons.solr to Solr 4.4
> -------------------------------
>
>                 Key: STANBOL-1162
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1162
>             Project: Stanbol
>          Issue Type: Improvement
>            Reporter: Rupert Westenthaler
>
> Some initial checks have showed that this update comes with API changes in 
> Solr that will affect several components:
> This I am currently aware of are:
> * solr.core: OsgiSolrCore, OsgiResourceLoader
> * Lucene based NLP components: as the API for creating Analyzer instances 
> changed
> * TopicEngine: need to adapt the unit tests to use the new API to create 
> CoreContainer

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to