[
https://issues.apache.org/jira/browse/OFBIZ-9440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071398#comment-16071398 ]
Pierre Smits commented on OFBIZ-9440:
-------------------------------------
The two components came in the OFBiz codebase from different angles/viewpoints.
Lucene (Core), according to [1], is an indexing and search engine , while the Sorl extends the Lucene functionality with some additional features.
I believe we, the community, need to take a decision. The first (Lucene) could be a framework indexing service, and the second could be were it is as an optional providing the search capabilities based on (and extending) the first set of functionalities. Or, alternatively, we ditch one of the two. And improve from there.
[1]
http://lucene.apache.org/> Refactor the Lucene and Solr Components
> ---------------------------------------
>
> Key: OFBIZ-9440
> URL:
https://issues.apache.org/jira/browse/OFBIZ-9440> Project: OFBiz
> Issue Type: Improvement
> Components: lucene, solr
> Affects Versions: Trunk
> Reporter: Michael Brohl
> Assignee: Michael Brohl
>
> The Lucene and Solr components has several issues which makes it untestable and unusable as a single plugin. I'm not even sure if this should be a bug or improvement issue.
> There are several file and data dependencies left which should be (re-)moved.
> The file runtime/indexes/index.properties should be moved to the solr component. The folder runtime/indexes should be removed, the components have to take care of creating their index path(s).
> This issue might receive some subtasks along this journey...
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Locked
