On 11/28/12, Apache Bloodhound <[email protected]> wrote: > Page "Proposals/BEP-0004/ResourceQuery" was added by andrej > Content: > -------8<------8<------8<------8<------8<------8<------8<------8<-------- > [...] > > Resource Query component will provide a !ResourceQuery.query method with the > following parameters: > * '''query''': query string e.g. “bla status:closed” or a parsed > representation of the query . For more information see [#query_syntax Query > syntax]. > * '''sort''': optional sorting > * '''boost''': optional list of fields with boost values e.g. {“id”: 1000, > “subject” :100, “description”:10}. Used only for score based sorting. > * '''filters''': optional list of terms. Usually can be cached by > underlying search framework. For example {“type”: “wiki”} > * '''fields''': list of fields to return > * optional paging fields: '''rows/start''' or '''page/pagesize''' fields > * '''facets''' - optional list of facet terms, can be field or expression. > > == Resource Query is not a report tool #notreport > 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. > [...] > > 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. > [...]
This is interesting because it seems to me that these subjects I kept from original message overlap with a work I'm trying to finish right now ... so, when I have a result I'll follow with two major concrete suggestions . ;) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article:
