incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject [Apache Bloodhound] Proposals/BEP-0004 modified
Date Fri, 25 Jan 2013 13:39:38 GMT
Page "Proposals/BEP-0004" was changed by andrej
Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0004?action=diff&version=18>
Revision 18
Comment: Add security on roadmap
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: Proposals/BEP-0004
=========================================================================
--- Proposals/BEP-0004 (version: 17)
+++ Proposals/BEP-0004 (version: 18)
@@ -112,8 +112,9 @@
 
 A new plugin bhsearch is introduced. The plugin architecture supports possibility to use
different search backends like Whoosh, Lucen and Solr. Since bhsearch plugin functionality
is isolated, development can be done on trunk. 
 
+[=#roadmap]
 === Current status
-[=#prototype] Current implementation is in prototype (alpha) phase. BloodhoundSearch page
describes current Bloodhound search functionality. In a few words:
+Current implementation is in prototype (alpha) phase. BloodhoundSearch page describes current
Bloodhound search functionality. In a few words:
  * Whoosh library is used for search index 
  * Support search in tickets, wiki pages and milestones
  * Support search by free text and query. For query syntax see wiki:Proposals/BEP-0004/ResourceQuery.
@@ -123,8 +124,9 @@
 === Beta phase
 Next release (Beta phase) should concentrate on code stability and the following features:
  * Add support for changesets
+ * Add security
  * Support pluggable schema generation.
- * Improve search quality
+ * Improve search quality based on feedback
  * Introduce quick search box
  * Improve index consistency. [=#consistency]  
    * Current implementation uses ITicketChangeListener interface that is triggered after
DB transaction is already committed. There is possiblity to get inconsistency between DB and
search index if index update fails. In this case reindex is required. One of the possible
solution is to contact Trac community with suggestion to introduce a new, within transaction,
 I<Resource>ChangingListener interface. During this event we can save changes into additional
table and than index changes in separate thread.
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0004>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

This is an automated message. Someone added your email address to be
notified of changes on 'Proposals/BEP-0004' page.
If it was not you, please report to .

Mime
View raw message