community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joachim Dreimann (JIRA)" <>
Subject [jira] [Updated] (COMDEV-93) Add Solr support to Bloodhound Search plugin
Date Tue, 18 Jun 2013 10:43:20 GMT


Joachim Dreimann updated COMDEV-93:

    Summary: Add Solr support to Bloodhound Search plugin  (was: [GSoC] Add Solr support to
Bloodhound Search plugin)
> Add Solr support to Bloodhound Search plugin
> --------------------------------------------
>                 Key: COMDEV-93
>                 URL:
>             Project: Community Development
>          Issue Type: New Feature
>            Reporter: Joachim Dreimann
>              Labels: bloodhound, gsoc2013, mentor, solr
> Apache Bloodhound is a software development collaboration tool, including issue tracking,
wiki and repository browsing (see: Bloodhound extends Trac
( with multiple product support, advanced search functionality,
ticket relations, a simpler installer and sleeker user interface. Apache Bloodhound recently
graduated from the Apache Incubator as a stand-alone Apache project. 
> Problem: 
> The Bloodhound Search plugins supports different search backends, but only Woosh has
been implemented so far.
> Proposed solution: 
> Bloodhound's current plugin implementation supports Whoosh search backend. Apache Solr
( ) can be used as alternative search backend for Bloodhound
Search when requirements are reliability, scalability and fault tolerance. Work towards integrating
Solr into Trac (which Bloodhound is based on) has already started and can probably be built
> Skills needed: 
> Bloodhound and Trac are written in Python, so a moderate dose of Python programing skills
are required. Apache Solr is written in Java so intermediate Java programming skills are probably
> References: 
> Link to the original issue: 
> More GSoC-related tasks for Bloodhound: 
> Guidelines for contributing to Apache Bloodhound: 

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:

View raw message