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/ResourceQuery modified
Date Wed, 05 Dec 2012 13:15:46 GMT
Page "Proposals/BEP-0004/ResourceQuery" was changed by andrej
Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0004/ResourceQuery?action=diff&version=2>
Revision 2
Comment: Based on dev list feedback, change meta keyword sign to "$"
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: Proposals/BEP-0004/ResourceQuery
=========================================================================
--- Proposals/BEP-0004/ResourceQuery (version: 1)
+++ Proposals/BEP-0004/ResourceQuery (version: 2)
@@ -23,7 +23,7 @@
 As it was discussed on dev mailing list, search and query serve a different purpose than
reports. Resource Query is not intended not provide complex SQL like expressions linke JOIN,
UNION etc. Resource Query will search through flattened resource representation. Query syntax
should support issue tracker specifics such as search through attachments, related tickets
etc.
 
 == Query Syntax #query_syntax
-Resource Query will accept [http://lucene.apache.org/core/old_versioned_docs/versions/2_9_1/queryparsersyntax.html
Lucene-like] syntax familiar to users of Solr, [http://packages.python.org/Whoosh/querylang.html
Whoosh], Haystack, [http://code.google.com/p/unladen-swallow/issues/searchtips Google Code]
and [http://confluence.jetbrains.com/display/YTD4/Search+and+Command+Attributes#SearchandCommandAttributes-GeneralSearchAttributes
YouTrack] with additional functions/meta tags specific for Bloodhound/Trac e.g. related tickets,
attachment etc.
+Resource Query will accept [http://lucene.apache.org/core/old_versioned_docs/versions/2_9_1/queryparsersyntax.html
Lucene-like] syntax familiar to users of Solr, [http://packages.python.org/Whoosh/querylang.html
Whoosh], Haystack, [http://code.google.com/p/unladen-swallow/issues/searchtips Google Code]
and [http://confluence.jetbrains.com/display/YTD4/Search+and+Command+Attributes#SearchandCommandAttributes-GeneralSearchAttributes
YouTrack] with additional functions/meta keyword specific for Bloodhound/Trac e.g. related
tickets, attachment etc.
 
 Default Resource Query operator is AND.
 
@@ -38,22 +38,22 @@
 
 Resource Query should support version changing, similar to WAS and CHANGED operator in JIRA
(https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-WAS, http://confluence.jetbrains.com/display/YTD4/Search+and+Command+Attributes)

 
-Other functions or meta tags can be used in query. Meta tags can be marked with specific
character e.g. “#” (similar to YouTrack special keywords - http://confluence.jetbrains.com/display/YTD4/Search+and+Command+Attributes#SearchandCommandAttributes-ShortcutKeywords):
- * #me - current user
- * #my - assigned to me
- * #currentProject
- * #ticket, #wiki etc.
- * date and time helper functions e.g. 2weeksago, 1yearago etc. 
+Other functions or meta keywords can be used in query. Meta keywords can be marked with specific
character "$" (similar to $USER keyword in the existing Trac Query - https://issues.apache.org/bloodhound/wiki/TracReports).
Meta keywords should be case insensitive:
+ * $USER or $me  - current logged user, can be used as term value variable e.g. assigned:#ME
+ * $my - can be used to add assigned:<currentUser> condition to query
+ * $currentProject - can be used to add condition project:<currentEnvironmentProject>
+ * $ticket, $wiki etc. - can be used to add condition to query e.g. type:ticket, type:wiki
etc.
 
-Indexing and query syntax must be easily extended by plugins. Here is not a complete list
of other possible meta tags that can be provided by additional plugins:
- * #resolved/unresolved - status:(resolved OR closed)
- * version aggregation e.g. earliestUnreleasedVersion
- * #hasAttachment
- * code:xxx ... - contains code in wiki format
- * #duplicated
- * #closed = status:closed
- * #yesterday
- * ...
+Indexing and query syntax must be easily extended by plugins. Here is not a complete list
of other possible meta keywords that can be provided by additional plugins:
+ * $resolved/unresolved - status:(resolved OR closed)
+ * version aggregation e.g. $earliestUnreleasedVersion
+ * $hasAttachment
+ * $duplicated
+ * $closed
+
+===  Date and time format and usage
+TBD... 
+date and time helper functions e.g. 2weeksago, 1yearago etc. 
 
 == Use cases #usecases
 === User uses free text search or query  in quick search box #usecase_freesearch
-------8<------8<------8<------8<------8<------8<------8<------8<--------

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

Mime
View raw message