You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Woonsan Ko (JIRA)" <je...@portals.apache.org> on 2011/04/16 10:44:05 UTC
[jira] [Commented] (JS2-1246) Solr based portlet search engine
[ https://issues.apache.org/jira/browse/JS2-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020573#comment-13020573 ]
Woonsan Ko commented on JS2-1246:
---------------------------------
Solr based Jetspeed search engine has been implemented.
If you copy /WEB-INF/assembly/alternate/search-embedded-solr-override.xml to /WEB-INF/assembly/override/ folder, then Jetspeed-2 will use embedded Solr engine instead of lucene engine.
Or If you copy /WEB-INF/assembly/alternate/search-http-solr-override.xml to /WEB-INF/assembly/override/ folder, then Jetspeed-2 will use an (external) http based Solr engine instead.
I'll keep this issue open until documentation is finished.
Woonsan
> Solr based portlet search engine
> --------------------------------
>
> Key: JS2-1246
> URL: https://issues.apache.org/jira/browse/JS2-1246
> Project: Jetspeed 2
> Issue Type: Improvement
> Affects Versions: 2.2.1
> Reporter: Woonsan Ko
> Assignee: Woonsan Ko
> Fix For: 2.2.2
>
>
> Solr based Jetspeed SearchEngine component would be a good option because Solr cares all the clustering/replication issues and has been well-proven technology. It will be more effective to leverage Solr than to implement something similar with Lucene. This doesn't mean replacing the current Lucene based SearchEngine component, but adding a new optional component based on Solr.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org