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] BloodhoundSearch modified
Date Thu, 17 Jan 2013 22:01:31 GMT
Page "BloodhoundSearch" was changed by andrej
Diff URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundSearch?action=diff&version=8>
Revision 8
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: BloodhoundSearch
=========================================================================
--- BloodhoundSearch (version: 7)
+++ BloodhoundSearch (version: 8)
@@ -27,16 +27,16 @@
 * Field specific query e.g. "status:new keyword:starter" (default operator is AND)
 * Boolean queries e.g. "test OR (status:new and keyword:starter)"
 
-Currently, only tickets with the following fields are indexed. Later more resources and fields
will be added.
+Currently, only tickets and wiki pages with the following fields are indexed. Later more
resources and fields will be added.
 
 Common fields for all resources:
- * id - resource id. For ticket it is ticket id, for wiki it will wiki name.
+ * id - resource id. For ticket it is ticket id, for wiki it will wiki page name.
  * type - resource type e.g. ticket, wiki etc.
  * product - product name
  * time - resource change time
  * author - resource author. For ticket it is ticket reporter.
- * content - ticket description
- *changes - currently, only ticket comments are indexed
+ * content - ticket description, wiki page content
+ * changes - currently, only ticket comments are indexed
 
 Ticket specific fields:
  * component
@@ -50,9 +50,9 @@
 
 Default query boosting is: id = 6, type = 2, summary = 5, author = 3, milestone = 2, keywords
= 2, component = 2, status = 2, content = 1, changes = 1, 
 
-== Prototype phase 1 limitations == #limitations
- * Only tickets are indexed. Wiki page indexing will be supported in near future.
- * UI does not support faceting and type specific presentation i.e. All | Ticket | Wiki
+== Prototype phase 2 limitations == #limitations
+ * Only tickets and wiki pages are indexed.
+ * UI does not support faceting
  * Search  does not support meta keywords 
  * Quick jump by ticket id and wiki name is not supported
  * Possible bugs and inconveniences expected for prototype 
@@ -61,7 +61,7 @@
 Please consider below not complete list of TODOs.
  * UI design for search results including facets and resource specific presentation. Initial
proposal can be found on [wiki:Proposals/BEP-0004#resultview BEP-0004]
  * Add facet support for search UI
- * Improve index quality e.d. add more resources in index (wiki, milestones etc.), index
more fields for ticket
+ * Improve index quality e.d. add more resources in index (milestones etc.), index more fields
for ticket. Support pluggable schema generation.
  * Improve search quality
  * Improve index consistency. [=#consistency]  
    * Current implementation uses ITicketChangeListener interface that triggers after DB committed.
There is some chances to get inconsistency between DB and index. In this case reindex is required.
One of the possible solution is contact Trac community to introduce a new within transaction
 I<Resource>ChangingListener interface, save changes into additional table and index
changes in separate thread.
-------8<------8<------8<------8<------8<------8<------8<------8<--------

--
Page URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundSearch>
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 'BloodhoundSearch' page.
If it was not you, please report to .

Mime
View raw message