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, 15 Feb 2013 16:33:12 GMT
Page "Proposals/BEP-0004" was changed by andrej
Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0004?action=diff&version=20>
Revision 20
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: Proposals/BEP-0004
=========================================================================
--- Proposals/BEP-0004 (version: 19)
+++ Proposals/BEP-0004 (version: 20)
@@ -121,19 +121,9 @@
  * UI provides search in all entries or in entries of specific resource type e.g. only in
Tickets
  * Facets are selected based on searched resource type
 
-=== Beta phase
+=== Beta phase #beta
 Next release (Beta phase) should concentrate on code stability and the following features:
 [[TicketQuery(keywords=~bep-0004-beta, format=table, col=id|summary|status|owner|milestone)]]
-
-Other features that are not yet reflected in tickets:
- * Add support for changesets
- * Add security
- * Support pluggable schema generation.
- * 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.
-   * Some ticket changes are not reflected in event interfaces e.g. Version and Component
renaming. One of the possible solution is to contact Trac community to introduce new interfaces.
-   * Alternative solution is triggering events from SQL proxy developed on multi-product
branch
-   * Usage of DB triggers is another alternative
 
 === Stable phase 
 Solution should be stable enough to be part of Bloodhound standard delivery and replace existing
search functionality. We can add more features 
-------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